For what it is worth, I have been using MyFaces 1.1.1 inside a web
application built via Maven 2.0.4. To upgrade to 1.1.3-SNAPSHOT of
MyFaces and Tomahawk I made the following changes to pom.xml
1) Removed the MyFaces 1.1.1 dependencies
<dependency>
<groupId>myfaces</groupId>
<artifactId>myfaces-impl</artifactId>
<version>1.1.1</version>
</dependency>
<dependency>
<groupId>myfaces</groupId>
<artifactId>tomahawk</artifactId>
<version>1.1.1</version>
</dependency>
2) Added MyFaces 1.1.3-SNAPSHOT dependencies. (Notice myfaces-api is a
new dependency)
<dependency>
<groupId>org.apache.myfaces.core</groupId>
<artifactId>myfaces-api</artifactId>
<version>1.1.3-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.myfaces.core</groupId>
<artifactId>myfaces-impl</artifactId>
<version>1.1.3-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.apache.myfaces.tomahawk</groupId>
<artifactId>tomahawk</artifactId>
<version>1.1.3-SNAPSHOT</version>
</dependency>
3) Added the Apache snapshot repository.
<repositories>
<repository>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>apache-maven-snapshots</id>
<url>http://cvs.apache.org/maven-snapshot-repository</url>
</repository>
</repositories>
The web application built cleanly and ran as expected.
Paul Spencer
Manfred Geiler wrote:
On 4/24/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I think this is the wrong way to fix it. I'm not sure what changing
the releases enabled to false does (maybe someone can answer that) but
here's the way I see the problem.
This IS the right way. Believe me.
The <snapshot> element without content is a syntax error - have a look at
maven docs!
What we try to tell Maven is:
Use the url http://cvs.apache.org/maven-snapshot-repository to download
snapshots, but do not use this url to seek release artifacts.
The correct syntax is to explicitly enable this repository for snapshots but
disable it for releases.
Actually when you build a custom project with a
myfaces-impl-1.1.2dependency Maven
2.0.4 tries to download the myfaces-master-1.0.1 release(!) from
http://cvs.apache.org/maven-snapshot-repository, which is subject to fail of
course.
Try it out!
This is the only build problem with the 1.1.2 core release. There is no
issue regarding myfaces-shared.
1.1.2 branch does not build b/c the myfaces-shared stuff is not in
ibiblio. Its ok that these shared artifacts are not in ibiblio
(that's what we wanted), they just need to be available in our own
MyFaces repository. (See my earlier post)
I think you got me wrong here. I did not try to build the 1.1.2 branch. What
I meant: when you build a project that DEPENDS on 1.1.2 core, then you run
into problems.
In the short run to build core-1.1.2 and core-1.1.3 you just need to
check out the appropriate shared and maven branches and build on your
local machine.
For all releases going forward I think we update the master pom stuff
and add a reference to a new myfaces repo which contains the shared
artifacts. That's actually why I'm holding off on the vote for the
1.1.3 core b/c we really need this going forward.
I'm going to revert your change for now.
Please leave my changes. They are ok.
We should also try to fix the releases myfaces-core-project-1.1.2.pom ASAP.
Manfred
On 4/24/06, Manfred Geiler <[EMAIL PROTECTED]> wrote:
The pom.xml of the myfaces-core-project artifact contains the following
errornous lines:
<repositories>
<repository>
<snapshots />
<id>apache-maven-snapshots</id>
<url>http://cvs.apache.org/maven-snapshot-repository</url>
</repository>
</repositories>
At least for the newest Maven 2.0.4 these lines make builds fail because
Maven tries to download the released(!) myfaces-master from the apache
snapshot(!) repo.
Correct syntax would be:
<repositories>
<repository>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>apache-maven-snapshots</id>
<url>http://cvs.apache.org/maven-snapshot-repository</url>
</repository>
</repositories>
Just corrected this on the 1.1.3 branch.
Sean, could you please build a new RC?
What about 1.1.2?
Is it possible to replace the already released
myfaces-core-project-1.1.2.pom? Shall I correct the 1.1.2 core branch?
Note: Without that correction nobody is able to build Maven projects
that
depend on myfaces-api-1.1.2 or myfaces-impl-1.1.2 !
Manfred
