Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.0.0.CR1, 3.1.0.Beta4
-
Fix Version/s: 3.1.0.CR1
-
Component/s: Shared Examples
-
Labels:None
-
Steps to Reproduce:
-
Workaround Description:
Description
The examples in seam-3.1.0.Beta4/examples, including the seam-booking example, cannot be built, as they reference parent POMs that are not in the distribution, .e.g
<parent>
<groupId>org.jboss.seam.examples</groupId>
<artifactId>seam-examples-parent</artifactId>
<version>3.1.0.Beta4</version>
<relativePath>../pom.xml</relativePath>
</parent>
in seam-3.1.0.Beta4/examples/seam-booking/pom.xml
or see any other example in the distribution...
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
If you are having trouble building the examples, follow the instructions in the link below to add the JBoss Maven repo to your settings.xml
http://community.jboss.org/wiki/MavenGettingStarted-Users
Keith Moore
added a comment - - edited If you are having trouble building the examples, follow the instructions in the link below to add the JBoss Maven repo to your settings.xml
http://community.jboss.org/wiki/MavenGettingStarted-Users I had a similar build problem when I shipped the examples for Metawidget. It makes for a poor 'out of the box' experience, and telling people to edit their settings.xml is pretty ugly. I think Seam 3 could do better. Maybe either:
1. Add a <repository> declaration to each example's pom.xml (I just tried this and it works)
2. Ship the seam-examples-parent pom.xml in the main Seam 3 distribution. Put it in the /examples folder, alongside the examples.txt (this is what I ended up doing for Metawidget)
Have either of these been considered?
Richard.
Richard Kennard
added a comment - I had a similar build problem when I shipped the examples for Metawidget. It makes for a poor 'out of the box' experience, and telling people to edit their settings.xml is pretty ugly. I think Seam 3 could do better. Maybe either:
1. Add a <repository> declaration to each example's pom.xml (I just tried this and it works)
2. Ship the seam-examples-parent pom.xml in the main Seam 3 distribution. Put it in the /examples folder, alongside the examples.txt (this is what I ended up doing for Metawidget)
Have either of these been considered?
Richard. Also, why has the seam-booking/readme.md file got an extension of '.md' instead of '.txt'? This may be a convention I've never heard of, but the other examples all have 'readme.txt'?
Richard Kennard
added a comment - Also, why has the seam-booking/readme.md file got an extension of '.md' instead of '.txt'? This may be a convention I've never heard of, but the other examples all have 'readme.txt'? As noted in the comments and other users' confusion on #seam, this issue cannot be considered as "fixed"
The root of the problem is that user downloading the Seam3 .zip distribution is required to add the jboss repository to his/her settings.xml, but this fact is not noted in any documentation in the .zip file.
Therefore, one of these two things are necessary:
1. Modify the POM files, adding the example parent pom to the distribution and enabling the jboss public repo there.
2. or; add a note to the docs distributed in the .zip file that enabling the jboss repository is required to make the examples work.
Marek Schmidt
added a comment - As noted in the comments and other users' confusion on #seam, this issue cannot be considered as "fixed"
The root of the problem is that user downloading the Seam3 .zip distribution is required to add the jboss repository to his/her settings.xml, but this fact is not noted in any documentation in the .zip file.
Therefore, one of these two things are necessary:
1. Modify the POM files, adding the example parent pom to the distribution and enabling the jboss public repo there.
2. or; add a note to the docs distributed in the .zip file that enabling the jboss repository is required to make the examples work. Is this still a problem?
Jason Porter
added a comment - Is this still a problem? I've now include the examples parent pom.xml in the distribution.
@Richard, we use MarkDown (the .md extension) because it allows us to introduce formatting into the file, and it is supported by GitHub (it will actually render correct when you browse to that project on the GitHub site).
Shane Bryzak
added a comment - I've now include the examples parent pom.xml in the distribution.
@Richard, we use MarkDown (the .md extension) because it allows us to introduce formatting into the file, and it is supported by GitHub (it will actually render correct when you browse to that project on the GitHub site). 
Released Maven artifacts for examples