Just had a look at the current api/pom.xml:
Somehow the necessary dependencies for the regenerate-component-code
profile got lost during a merge/release. Sean, did you do that by
intention or can this be a bug in the maven release plugin?
However, this is the correct plugin configuration:
<profile>
<id>regenerate-component-code</id>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>regenerate-component-code-parts</id>
<phase>process-sources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<property value="${project.basedir}/src/main/java"
name="src.dir"></property>
<ant inheritRefs="true" inheritAll="true"
antfile="build.xml" dir="${project.basedir}">
<target name="generate-components"></target>
</ant>
</tasks>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>velocity</groupId>
<artifactId>velocity</artifactId>
<version>1.4</version>
</dependency>
<dependency>
<groupId>org.apache.myfaces.maven</groupId>
<artifactId>build-tools</artifactId>
<version>1.0.4-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</profile>
I just added the missing lines to the current head.
Don't know what is the correct way to fix that for the jsf12 branch:
- add the <dependencies> there as well, or
- merge trunk to branch?
Another issue:
Sean, why was the version number adjusted to 1.0.4-SNAPSHOT?!
IMO it makes no sense to increase the release number for the
build-tools subproject.
We should rather release and freeze it at final 1.0.0 as long as there
is no change. This way we will have a jar in the public maven repo and
there are no more build problems.
BTW, the same applies for the wagon-maven-plugin. Why increase the
version number on every core or tomahawk release?
So, I propose to officially release build-tools and wagon-maven-plugin
with a final version number and freeze all dependencies in the various
poms. This way the release process will get easier, too, right?
Manfred
On 5/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> Matze, as a workaround please checkout the current maven subproject
> and build it first. As soon as you have the
> build-tools-1.0.0-SNAPSHOT.jar in your local maven repo the codegen
> task should work for you.
Well, I build that guy and 1.0.4-SNAPSHOT.jar is in my local m2 repo
(~/.m2/repository/org/apache/myfaces/maven/build-tools/1.0.4-SNAPSHOT)
What is the
-Matthias
> Regards,
> Manfred
>
>
> On 5/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I just tried to run the code generator against the JSF 1.2 brunch.
> > (after "mvn clean install" for maven/build-tools)
> >
> > I now get this *error*, since I think something inside the build.xml
> > (or on my box) is wrong
> >
> > build.xml sniplet:
> > <taskdef name="generate"
> > classname="org.apache.myfaces.codegen.component.ComponentGeneratorTask">
> > <classpath refid="maven.plugin.classpath"/>
> > </taskdef>
> >
> >
> > ERROR:
> >
> > generate-components:
> > [INFO]
----------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
----------------------------------------------------------------------------
> > [INFO] Error executing ant tasks
> >
> > Embedded error: The following error occurred while executing this line:
> > /home/matzew/workspace/jsf12/api/build.xml:5: taskdef class
> > org.apache.myfaces.codegen.component.ComponentGeneratorTask cannot be
> > found
> > [INFO]
----------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
----------------------------------------------------------------------------
> > [INFO] Total time: 4 seconds
> > [INFO] Finished at: Wed May 31 07:25:40 CEST 2006
> > [INFO] Final Memory: 3M/7M
> > [INFO]
----------------------------------------------------------------------------
> >
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
