RE: Using Maven as Eclipse class-path container

[Jörg Schaible]

Marcel Schutte wrote on Tuesday, November 08, 2005 8:48 AM:

> Sounds like a good idea. I think the eclipse plugin works
> only in the opposite direction, generating .classpath etc
> files for eclipse to use. A problem might be that eclipse
> doesn't have the concept of scopes for its dependencies.

It has. You can define dependencies to be "exported".

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Using Maven as Eclipse class-path container

[Marcel Schutte]

Sounds like a good idea. I think the eclipse plugin works only in the
opposite direction, generating .classpath etc files for eclipse to use.
A problem might be that eclipse doesn't have the concept of scopes for
its dependencies.

Marcel

--- Michael Böckling <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> I'd like to know if there is, or if there are any plans to create, an
> 
> Eclipse plugin that cann add a Maven2 class-path container to a
> project, 
> so there is a way to use the Maven artifact resolver (adding 
> dependencies automatically to the Eclipse classpath) inside Eclipse. 
> This would be especially useful for transitive depencies...
> The idea for this stems from the Necessitas Ivy plugin for Eclipse:
>
http://kevin.oneill.id.au/2005/06/06/necessitas-jar-management-for-eclipse
> 
> Are there any informations about this topic? Maybe the soon-to-be 
> released M2 Eclipse plugin 
> (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do
> this?
> 
> Thanks,
> Michael Böckling
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 





__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] ant bug with EnumeratedAttribute task parameters=

[Anuerin Diaz]

ok, the mvn clean install did not work. so just to get going i just
extracted the manifest folder of the original plugin jar and added it
manually to the hijacked jar. i am still stumped on this stack trace
even if the same buildfile executes perfectly fine with the same jar
file...

=
Embedded error: The following error occurred while executing this line:
C:\Temp\workdir\sample-plugin\build.xml:9: Class
sample.ant.ComplexTask doesn't support the "parameter" attribute.
[INFO] 

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
executing ant tasks
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301
)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
executing ant tasks
at 
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:66)
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:60)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
... 16 more
Caused by: The following error occurred while executing this line:
C:\Temp\workdir\sample-plugin\build.xml:9: Class
sample.ant.ComplexTask doesn't support the "parameter" attribute.
at 
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:388)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at 
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:60)
... 19 more
Caused by: C:\Temp\workdir\sample-plugin\build.xml:9: Class
sample.ant.ComplexTask doesn't support the "parameter" attribute.

at 
org.apache.tools.ant.IntrospectionHelper.setAttribute(IntrospectionHelper.java:516)
at 
org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:368)
at 
org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:322)
at org.apache.tools.ant.Task.maybeConfigure(Task.java:254)
at 
org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:189)
at 
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:158)
at org.apache.tools.ant.Task.perform(Task.java:363)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:386)
... 23 more
=

ciao!


On 11/8/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> not really but is it the same if I did a "mvn clean package" and "mvn
> install"? sounds weird but since i was using a customized settings
> file i created a batch file to do the "clean package" step in one
> call.
>
>  i have also tried deleting the plugin folder in my local repository
> to ensure that the jar file is being copied. anyway i will try doing
> the "clean install" later when i get to the office and see what
> happens. i am just a little bit puzzled why my own jar file did not
> have those two files and i a

Re: [m2] NullPointerException running maven package

[Brett Porter]

Fixed in SVN.

(There is another problem it is trying to report, but the cause was unknown).

- Brett

On 11/8/05, Michael McCrann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Has anyone seen the NullPointerException, below, before?
>
> I have searched for it in Nabble, but I can't find any references to it.
>
> Michael McCrann
>
> [INFO] [surefire:test]
> [INFO] Setting reports dir:
> c:\maven_projects\myhome\target\checkout\target/surefire-reports
> [INFO]
> 
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> 
> ---
> constituent[0]: file:/c:/applications/maven-2.0/lib/commons-cli-1.0.jar
> constituent[1]:
> file:/c:/applications/maven-2.0/lib/doxia-sink-api-1.0-alpha-4.jar
> constituent[2]: file:/c:/applications/maven-2.0/lib/jsch-0.1.23.jar
> constituent[3]:
> file:/c:/applications/maven-2.0/lib/maven-artifact-2.0-1.jar
> constituent[4]:
> file:/c:/applications/maven-2.0/lib/maven-artifact-manager-2.0-1.jar
> constituent[5]: file:/c:/applications/maven-2.0/lib/maven-core-2.0.jar
> constituent[6]:
> file:/c:/applications/maven-2.0/lib/maven-error-diagnostics-2.0.jar
> constituent[7]: file:/c:/applications/maven-2.0/lib/maven-model-2.0.jar
> constituent[8]:
> file:/c:/applications/maven-2.0/lib/maven-monitor-2.0.jar
> constituent[9]:
> file:/c:/applications/maven-2.0/lib/maven-plugin-api-2.0.jar
> constituent[10]:
> file:/c:/applications/maven-2.0/lib/maven-plugin-descriptor-2.0.jar
> constituent[11]:
> file:/c:/applications/maven-2.0/lib/maven-plugin-parameter-documenter-2.
> 0.jar
> constituent[12]:
> file:/c:/applications/maven-2.0/lib/maven-plugin-registry-2.0.jar
> constituent[13]:
> file:/c:/applications/maven-2.0/lib/maven-profile-2.0.jar
> constituent[14]:
> file:/c:/applications/maven-2.0/lib/maven-project-2.0-1.jar
> constituent[15]:
> file:/c:/applications/maven-2.0/lib/maven-reporting-api-2.0.jar
> constituent[16]:
> file:/c:/applications/maven-2.0/lib/maven-repository-metadata-2.0.jar
> constituent[17]:
> file:/c:/applications/maven-2.0/lib/maven-settings-2.0.jar
> constituent[18]:
> file:/c:/applications/maven-2.0/lib/plexus-interactivity-api-1.0-alpha-4
> .jar
> constituent[19]:
> file:/c:/applications/maven-2.0/lib/wagon-file-1.0-alpha-5.jar
> constituent[20]:
> file:/c:/applications/maven-2.0/lib/wagon-http-lightweight-1.0-alpha-5.j
> ar
> constituent[21]:
> file:/c:/applications/maven-2.0/lib/wagon-provider-api-1.0-alpha-5.jar
> constituent[22]:
> file:/c:/applications/maven-2.0/lib/wagon-ssh-1.0-alpha-5.jar
> ---
> java.lang.NullPointerException
> at
> org.apache.maven.usability.diagnostics.DiagnosisUtils.appendRootCauseIfP
> resentAndUnique(DiagnosisUtils.java:8
> 9)
> at
> org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(Mojo
> ExecutionExceptionDiagnoser.java:66)
> at
> org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(ErrorDi
> agnostics.java:81)
> at
> org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:693)
> at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:640)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:119)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO]
> 
> 
> [INFO] Total time: 14 seconds
> [INFO] Finished at: Tue Nov 08 16:10:05 EST 2005
> [INFO] Final Memory: 3M/5M
> [INFO]
> 
> 
>
>
> NOTICE
> This e-mail and any attachments are confidential and may contain copyright 
> material of Macquarie Bank or third parties. If you are not the intended 
> recipient of this email you should not read, print, re-transmit, store or act 
> in reliance on this e-mail or any attachments, and should destroy all copies 
> of them. Macquarie Bank does not guarantee the integrity of any emails or any 
> attached files. The views or opinions expressed are the author's own and may 
> not reflect the views or opinions of Macqua

[m2] NullPointerException running maven package

[Michael McCrann]

Hi,

Has anyone seen the NullPointerException, below, before?

I have searched for it in Nabble, but I can't find any references to it.

Michael McCrann

[INFO] [surefire:test]
[INFO] Setting reports dir:
c:\maven_projects\myhome\target\checkout\target/surefire-reports
[INFO]


[ERROR] BUILD ERROR
[INFO]


---
constituent[0]: file:/c:/applications/maven-2.0/lib/commons-cli-1.0.jar
constituent[1]:
file:/c:/applications/maven-2.0/lib/doxia-sink-api-1.0-alpha-4.jar
constituent[2]: file:/c:/applications/maven-2.0/lib/jsch-0.1.23.jar
constituent[3]:
file:/c:/applications/maven-2.0/lib/maven-artifact-2.0-1.jar
constituent[4]:
file:/c:/applications/maven-2.0/lib/maven-artifact-manager-2.0-1.jar
constituent[5]: file:/c:/applications/maven-2.0/lib/maven-core-2.0.jar
constituent[6]:
file:/c:/applications/maven-2.0/lib/maven-error-diagnostics-2.0.jar
constituent[7]: file:/c:/applications/maven-2.0/lib/maven-model-2.0.jar
constituent[8]:
file:/c:/applications/maven-2.0/lib/maven-monitor-2.0.jar
constituent[9]:
file:/c:/applications/maven-2.0/lib/maven-plugin-api-2.0.jar
constituent[10]:
file:/c:/applications/maven-2.0/lib/maven-plugin-descriptor-2.0.jar
constituent[11]:
file:/c:/applications/maven-2.0/lib/maven-plugin-parameter-documenter-2.
0.jar
constituent[12]:
file:/c:/applications/maven-2.0/lib/maven-plugin-registry-2.0.jar
constituent[13]:
file:/c:/applications/maven-2.0/lib/maven-profile-2.0.jar
constituent[14]:
file:/c:/applications/maven-2.0/lib/maven-project-2.0-1.jar
constituent[15]:
file:/c:/applications/maven-2.0/lib/maven-reporting-api-2.0.jar
constituent[16]:
file:/c:/applications/maven-2.0/lib/maven-repository-metadata-2.0.jar
constituent[17]:
file:/c:/applications/maven-2.0/lib/maven-settings-2.0.jar
constituent[18]:
file:/c:/applications/maven-2.0/lib/plexus-interactivity-api-1.0-alpha-4
.jar
constituent[19]:
file:/c:/applications/maven-2.0/lib/wagon-file-1.0-alpha-5.jar
constituent[20]:
file:/c:/applications/maven-2.0/lib/wagon-http-lightweight-1.0-alpha-5.j
ar
constituent[21]:
file:/c:/applications/maven-2.0/lib/wagon-provider-api-1.0-alpha-5.jar
constituent[22]:
file:/c:/applications/maven-2.0/lib/wagon-ssh-1.0-alpha-5.jar
---
java.lang.NullPointerException
at
org.apache.maven.usability.diagnostics.DiagnosisUtils.appendRootCauseIfP
resentAndUnique(DiagnosisUtils.java:8
9)
at
org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(Mojo
ExecutionExceptionDiagnoser.java:66)
at
org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(ErrorDi
agnostics.java:81)
at
org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:693)
at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:640)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:119)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]


[INFO] BUILD SUCCESSFUL
[INFO]


[INFO] Total time: 14 seconds
[INFO] Finished at: Tue Nov 08 16:10:05 EST 2005
[INFO] Final Memory: 3M/5M
[INFO]




NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.

Re: [m1] Problems resolving external dtd reference

[Phil Steitz]

Lukas Theussl wrote:

This is a known issue: http://jira.codehaus.org/browse/MPXDOC-179

For stand-alone projects, you can make it work by specifying an absolute 
path for the external entity, but this will not work in a multiproject 
set-up. Otherwise, I'm afraid I can't offer anything else right now.


Thanks.  Unfortunately absolute path will not work for this. It is odd, 
though, that I am using the same version (1.9.2) of the xdoc plugin in 
both cases and it only fails under 1.1-beta-2. Must be the parser or 
something to do with the context that the plugin gets the resource.


I am interested in others' approaches to handling common menus shared by 
multiple projects.  I don't like the entity reference approach that we 
use in commons now and am thinking about writing a plugin to do things 
in a cleaner way.  I would be interested in ideas on how best to 
approach this.


Phil


-Lukas


Phil Steitz wrote:

After installing 1.1-beta-2, the following external reference 
(included in navigation.xml files) that we use to include common menus 
on the Jakarta Commons sites is no longer working:


'../../commons-build/menus/menus.dtd'>


The xdoc plugin generates the following error:

Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved 
without a base URI.


Any ideas how to work around this?  Any better ideas on how to include 
common menus and portions thereof on multiple sites?  The commons 
sites indivdual navigation.xml files refer to entities defined in the 
dtd referenced above, so common elements can be maintained in one place.


Thanks in advance.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1] Problems resolving external dtd reference

[Brett Porter]

A "solution" is to include your own endorsed copy of Xerces in the JRE/Maven.

I have no idea why the behaviour is different though.

- Brett

On 11/8/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> This is a known issue: http://jira.codehaus.org/browse/MPXDOC-179
>
> For stand-alone projects, you can make it work by specifying an absolute
> path for the external entity, but this will not work in a multiproject
> set-up. Otherwise, I'm afraid I can't offer anything else right now.
>
> -Lukas
>
>
> Phil Steitz wrote:
> > After installing 1.1-beta-2, the following external reference (included
> > in navigation.xml files) that we use to include common menus on the
> > Jakarta Commons sites is no longer working:
> >
> >  > '../../commons-build/menus/menus.dtd'>
> >
> > The xdoc plugin generates the following error:
> >
> > Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved
> > without a base URI.
> >
> > Any ideas how to work around this?  Any better ideas on how to include
> > common menus and portions thereof on multiple sites?  The commons sites
> > indivdual navigation.xml files refer to entities defined in the dtd
> > referenced above, so common elements can be maintained in one place.
> >
> > Thanks in advance.
> >
> > Phil
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m1] Problems resolving external dtd reference

[Lukas Theussl]

This is a known issue: http://jira.codehaus.org/browse/MPXDOC-179

For stand-alone projects, you can make it work by specifying an absolute 
path for the external entity, but this will not work in a multiproject 
set-up. Otherwise, I'm afraid I can't offer anything else right now.


-Lukas


Phil Steitz wrote:
After installing 1.1-beta-2, the following external reference (included 
in navigation.xml files) that we use to include common menus on the 
Jakarta Commons sites is no longer working:


'../../commons-build/menus/menus.dtd'>


The xdoc plugin generates the following error:

Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved 
without a base URI.


Any ideas how to work around this?  Any better ideas on how to include 
common menus and portions thereof on multiple sites?  The commons sites 
indivdual navigation.xml files refer to entities defined in the dtd 
referenced above, so common elements can be maintained in one place.


Thanks in advance.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m1] Problems resolving external dtd reference

[Phil Steitz]

After installing 1.1-beta-2, the following external reference (included 
in navigation.xml files) that we use to include common menus on the 
Jakarta Commons sites is no longer working:


'../../commons-build/menus/menus.dtd'>


The xdoc plugin generates the following error:

Relative URI '../../commons-build/menus/menus.dtd' cannot be resolved 
without a base URI.


Any ideas how to work around this?  Any better ideas on how to include 
common menus and portions thereof on multiple sites?  The commons sites 
indivdual navigation.xml files refer to entities defined in the dtd 
referenced above, so common elements can be maintained in one place.


Thanks in advance.

Phil

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] ant bug with EnumeratedAttribute task parameters=

[Anuerin Diaz]

not really but is it the same if I did a "mvn clean package" and "mvn
install"? sounds weird but since i was using a customized settings
file i created a batch file to do the "clean package" step in one
call.

 i have also tried deleting the plugin folder in my local repository
to ensure that the jar file is being copied. anyway i will try doing
the "clean install" later when i get to the office and see what
happens. i am just a little bit puzzled why my own jar file did not
have those two files and i already reviewed the pom files for the
antrun plugin and its parent. i maybe too green in the gills but i
dont see any special configuration to have it included.

ciao!

On 11/8/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Did you run "mvn clean install" to install it?
>
> - Brett
>
> On 11/8/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > hi again,
> >
> >im trying to debug the problem below (hoping i can find a
> > workaround) but since policy prevents me from installing subversion in
> > my workstation (even if it doesnt entail a real installer), i just
> > manually retrieved the maven-antrun-plugin from
> > http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-antrun-plugin/
> >
> >   i am pretty sure that i have copied the correct structure (sans the
> > site directory) and the latest versions of each source/resource
> > file[1]. i edited the pom and based it on the pom included in the
> > original antrun plugin jar file. my project pom looks like this
> >
> >   org.apache.maven.plugins
> >   maven-antrun-plugin
> >   maven-plugin
> >   Maven AntRun Plugin
> >   1.0
> >
> >   
> > 
> >   org.apache.maven
> >   maven-plugin-tools-api
> >   2.0
> > 
> > 
> >   ant
> >   ant
> >   1.6.2
> > 
> >
> >   
> >
> >
> > i just inserted some printout statements to help get an idea how
> > things are done (my java skills need some more work). the 'impromptu'
> > project compiles and installs fine in my local repository but using
> > the plugin causes this error:
> >
> > 
> > [ERROR] Nonexistent component:
> > org.codehaus.plexus.component.configurator.ComponentConfiguratoroverride
> > [INFO] 
> > 
> > [ERROR] BUILD ERROR
> > [INFO] 
> > 
> > [INFO] Internal error in the plugin manager executing goal
> > 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run': Unable to find
> > the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the
> > plugin 'org.apache.maven.plugins:maven-antrun-plugin'
> >
> > Component descriptor cannot be found in the component repository:
> > org.codehaus.plexus.component.configurator.ComponentConfigu
> > ratoroverride.
> > ==
> >
> > i noticed that the original plugin jar file has the
> > META-INF/plexus/component.xml and META-INF/maven/plugin.xml. My
> > 'hijacked'  antrun plugin does no thave these files. can you point to
> > me what i missed? thanks.
> >
> >
> > [1] dir /s /b /a-d antrun\src
> > src\main\java\org\apache\maven\plugin\antrun\AbstractAntMojo.java
> > src\main\java\org\apache\maven\plugin\antrun\AntPropertyHelper.java
> > src\main\java\org\apache\maven\plugin\antrun\AntRunMojo.java
> > src\main\java\org\apache\maven\plugin\antrun\components\AntTargetConverter.java
> > src\resources\META-INF\plexus\components.xml
> >
> > ciao!
> >
> >
> > On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > > hi,
> > >
> > >  the attachments caused my mail to bounce so you can access the files
> > > using this link (combined to a single file, 8KB in total) :
> > >
> > >http://ramfree17.org/hasty/maven/antrun_issue.zip
> > >
> > >
> > > ciao!
> > >
> > > On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > > > hi,
> > > >
> > > >  the ant-run plugin (or the launcher) seems unable to properly
> > > > convert attributes that are of the type EnumeratedAttribute[1]. the
> > > > execution always fail with an error that the attribute being set is
> > > > not supported by the class.
> > > >
> > > >  i have attached 3 files to serve as a test case for this.
> > > >
> > > >  1. "sample.zip" - contains the project that will serve as the main
> > > > test case. it really is just the plugin tutorial and i just added the
> > > > followign in the pom.xml so my test Task will be called during compile
> > > > time:
> > > >
> > > > 
> > > >   
> > > >
> > > >testbed
> > > >tests
> > > >1.0
> > > >
> > > >
> > > >ant
> > > >ant
> > > >1.5
> > > >
> > > >   
> > > >  
> > > > 
> > > >maven-antrun-plugin
> > > >
> > > >   
> > > >  compile
> > > > 
> > > >
> > > >> > >   target = "te

[m102] strange compile error

[luan xl]

I used the "maven eclipse" to generate the eclipse project, and in the IDE 
everything is fine, compile is ok and unit test is ok. but when I switch 
back to using maven:


maven -X java:compile

the compiler can not find getTextContent() method in org.w3c.dom.Node, and 
point the following statement as an error:

  code += childList.item(i).getTextContent().hashCode() * 5L;

and I also tried "maven ant" to produce the ant build.xml, then I compile, 
test, everything is also ok.


so it that a bug?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [m2] module paths for system scope are relative to parent pom

[Jeff Jensen]

Sorry, but I still have not solved this problem...
Does anyone know how to?


-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 06, 2005 11:23 AM
To: 'Maven Users List'
Subject: [m2] module paths for system scope are relative to parent pom

When building from the parent POM dir, all paths are relative to it.  A
problem occurs when its modules have dependencies of system -
the module's corresponding  is relative to the parent POM dir,
instead of the module's POM dir.

With a module's  set to compile correctly it on its own,
compiling from its parent POM dir gives this error:

[INFO] Failed to resolve artifact.

GroupId: thegrp
ArtifactId: subsystem
Version: 2.1-SNAPSHOT

Reason: System artifact: thegrp:subsystem:jar:2.1-SNAPSHOT not found in
path: src\lib\subsystem.jar
  thegrp:subsystem:2.1-SNAPSHOT:jar

(would be nice to have the fully qualified path name listed there, instead
of the relative one so users would know where it is really looking for it
from)


Is this "Working As Designed"?

Is this the correct way to approach this, or what don't I know about yet??!

Is there a way to get this to work as I am trying to (e.g. a ${} variable
available to use in the modules dependency )?


Also, Is there a page that lists all of the available ${} variables?  I
could not find one...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Independent Subprojects in Maven

[Brett Porter]

It is a command line switch. Sorry, there is currently no way to
configure it as part of the project.

See mvn --help for more details.

- Brett

On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> In which file do I put the --fail-at-end switch?
>
> Sorry I am new to Maven
>
> Ashley
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 08, 2005 1:23 PM
> To: Maven Users List
> Subject: Re: Independent Subprojects in Maven
>
> Yes.
>
> - Brett
>
> On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> > Car project and truck project are independent of each other.
> > I have one person working on the truck project and another person
> > working on the car project. I have a nightly built running everyday to
> > compile each project and build the maven site. Sometimes the person
> > responsible for the truck project forgets to check in a file and the
> > truck project fail to compile which in turns prevent the maven site
> > from being built thus preventing the car project person from using maven.
> >
> > I still want to see the maven site even though either one of the
> > project has failed to compile.
> >
> > Can the --fail-at-end switch be used in this case?
> >
> > Ashley
> >
> > -Original Message-
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, November 08, 2005 1:02 PM
> > To: Maven Users List
> > Subject: Re: Independent Subprojects in Maven
> >
> > I think you want the --fail-at-end switch.
> >
> > However, if trunk depends on car, it will still not build if car doesn't.
> >
> > Note that if it is just the tests failing, you can run "mvn compile"
> > from the top level and all projects will be compiled, then you can
> > proceed to test, etc.
> >
> > - Brett
> >
> > On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> > >
> > > I am trying sub project to my main project. For example, I have a
> > > rental
> > > project(main) and I want to add a truck project and a car project
> > > which are independent of the Main project. The problem I am having
> > > is when I build maven and the car project does not compile, the
> > > truck project gets affected and maven does not build.
> > >
> > > Can anyone help me with that?
> > >
> > >
> > > 
> > > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Independent Subprojects in Maven

[Ashley Hurkoo]

In which file do I put the --fail-at-end switch?

Sorry I am new to Maven

Ashley

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 1:23 PM
To: Maven Users List
Subject: Re: Independent Subprojects in Maven

Yes.

- Brett

On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> Car project and truck project are independent of each other.
> I have one person working on the truck project and another person 
> working on the car project. I have a nightly built running everyday to 
> compile each project and build the maven site. Sometimes the person 
> responsible for the truck project forgets to check in a file and the 
> truck project fail to compile which in turns prevent the maven site 
> from being built thus preventing the car project person from using maven.
>
> I still want to see the maven site even though either one of the 
> project has failed to compile.
>
> Can the --fail-at-end switch be used in this case?
>
> Ashley
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 08, 2005 1:02 PM
> To: Maven Users List
> Subject: Re: Independent Subprojects in Maven
>
> I think you want the --fail-at-end switch.
>
> However, if trunk depends on car, it will still not build if car doesn't.
>
> Note that if it is just the tests failing, you can run "mvn compile"
> from the top level and all projects will be compiled, then you can 
> proceed to test, etc.
>
> - Brett
>
> On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> >
> > I am trying sub project to my main project. For example, I have a 
> > rental
> > project(main) and I want to add a truck project and a car project 
> > which are independent of the Main project. The problem I am having 
> > is when I build maven and the car project does not compile, the 
> > truck project gets affected and maven does not build.
> >
> > Can anyone help me with that?
> >
> >
> > 
> > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Independent Subprojects in Maven

[Brett Porter]

Yes.

- Brett

On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> Car project and truck project are independent of each other.
> I have one person working on the truck project and another person working on
> the car project. I have a nightly built running everyday to compile each
> project and build the maven site. Sometimes the person responsible for the
> truck project forgets to check in a file and the truck project fail to
> compile which in turns prevent the maven site from being built thus
> preventing the car project person from using maven.
>
> I still want to see the maven site even though either one of the project has
> failed to compile.
>
> Can the --fail-at-end switch be used in this case?
>
> Ashley
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 08, 2005 1:02 PM
> To: Maven Users List
> Subject: Re: Independent Subprojects in Maven
>
> I think you want the --fail-at-end switch.
>
> However, if trunk depends on car, it will still not build if car doesn't.
>
> Note that if it is just the tests failing, you can run "mvn compile"
> from the top level and all projects will be compiled, then you can proceed
> to test, etc.
>
> - Brett
>
> On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
> >
> > I am trying sub project to my main project. For example, I have a
> > rental
> > project(main) and I want to add a truck project and a car project
> > which are independent of the Main project. The problem I am having is
> > when I build maven and the car project does not compile, the truck
> > project gets affected and maven does not build.
> >
> > Can anyone help me with that?
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Independent Subprojects in Maven

[Ashley Hurkoo]

Car project and truck project are independent of each other.
I have one person working on the truck project and another person working on
the car project. I have a nightly built running everyday to compile each
project and build the maven site. Sometimes the person responsible for the
truck project forgets to check in a file and the truck project fail to
compile which in turns prevent the maven site from being built thus
preventing the car project person from using maven.

I still want to see the maven site even though either one of the project has
failed to compile.

Can the --fail-at-end switch be used in this case?

Ashley

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 1:02 PM
To: Maven Users List
Subject: Re: Independent Subprojects in Maven

I think you want the --fail-at-end switch.

However, if trunk depends on car, it will still not build if car doesn't.

Note that if it is just the tests failing, you can run "mvn compile"
from the top level and all projects will be compiled, then you can proceed
to test, etc.

- Brett

On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
>
> I am trying sub project to my main project. For example, I have a 
> rental
> project(main) and I want to add a truck project and a car project 
> which are independent of the Main project. The problem I am having is 
> when I build maven and the car project does not compile, the truck 
> project gets affected and maven does not build.
>
> Can anyone help me with that?
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] - maven-release-plugin cannot load SCM provider

[Brett Porter]

Ah, sorry for the confusion.

nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
it is an SVN specific property.

- Brett

On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> This is the feedback I got from running mvn release:prepare
>
> [INFO] [release:prepare]
> [INFO] What tag name should be used?
> 0.1.2
> [INFO] Tagging release with the label 0.1.2.
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Error resolving case of 
> 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> s\my_repo\bug-control-model\tags\0.1.2'
>
> [INFO] 
> -
> ---
> [ERROR] BUILD ERROR
> [INFO] 
> -
> ---
> [INFO] An error is occurred in the tag process.
>
>
> The URL for the tagBase is identical to the URL supplied within the
> developerConnection element but "tags" replaces "trunk".
>
> Trent
>
>
> On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > The bug is for the default of ../tags when used instead of a tagbase
> > as you have, so it is different.
> >
> > Above that exception, there should have been output from the svn
> > command. Does that reveal anything?
> >
> > - Brett
> >
> > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > work with the previous revision of my file and this did not have a SCM
> > > URL defined.  I have been able to get the plugin to prompt me for
> > > input regarding the tags, but I am falling over in the tagging process
> > > with the following exception:
> > >
> > > Is this the same exception that has lead to the creation of the
> > > following issue in jira?
> > >
> > > http://jira.codehaus.org/browse/MNG-883
> > >
> > >
> > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is 
> > > occurred in
> > > the tag process.
> > >
> > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is 
> > > occurred
> > > in the tag process.
> > > at 
> > > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > eReleaseMojo.java:1414)
> > > at 
> > > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > leaseMojo.java:246)
> > >
> > >
> > > thanks for taking to time to look into this.
> > > Trent
> > >
> > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > I thought I had used windows paths in the SCM URL before without
> > > > issues, but its worth trying:
> > > >
> > > > scm|svn|file:///d:/subversion...
> > > >
> > > > hth,
> > > > Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > > This is the SCM URL for the project:
> > > > >
> > > > > 
> > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> > > > > 
> > > > >
> > > > > and the plugin is configured with the following tagbase element:
> > > > >
> > > > > 
> > > > > org.apache.maven.plugins
> > > > > maven-release-plugin
> > > > > 2.0-beta-3
> > > > > 
> > > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags
> > > > > 
> > > > > 
> > > > >
> > > > >
> > > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > > > They both use the same library - so the release plugin is for
> > > > > > automating release related tasks, the scm plugin for development
> > > > > > related tasks.
> > > > > >
> > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > there is still something wrong with it.
> > > > > >
> > > > > > - Brett
> > > > > >
> > > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > > > > Thanks for the reply.
> > > > > > > When I started to use the plugin I was prefixing the URLs with
> > > > > > > "scm:svn", but then I still had a problem so thought about 
> > > > > > > exploring
> > > > > > > and that is why I asked about setting the scm provider in a 
> > > > > > > different
> > > > > > > manner.  I have again used these prefixes and I still get a 
> > > > > > > problem.
> > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 
> > > > > > > of the plugin.
> > > > > > >
> > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > release plugin are similar.  Is it right to think that the 
> > > > > > > maven-scm
> > > > > > > plugin is planned to allow developers to aquire a project without 
> > > > > > > a
> > > > > > > pom.xml and then to complete the every day version control tasks?
> > > > > > > With this in mind is it best to view the maven-release plugin as a
> > > > > > > component that should be used to release code for a repository 
> > > > > > > instead
> > > > > > > of completing a checkout/checkin, copy etc manually?  I just want 
> > > > > > > to
> > > > > > > know the thoughts behind each plugin.
> > > > > > >
> > > > > > > ---

Re: Independent Subprojects in Maven

[Brett Porter]

I think you want the --fail-at-end switch.

However, if trunk depends on car, it will still not build if car doesn't.

Note that if it is just the tests failing, you can run "mvn compile"
from the top level and all projects will be compiled, then you can
proceed to test, etc.

- Brett

On 11/8/05, Ashley Hurkoo <[EMAIL PROTECTED]> wrote:
>
> I am trying sub project to my main project. For example, I have a rental
> project(main) and I want to add a truck project and a car project which are
> independent of the Main project. The problem I am having is when I build
> maven and the car project does not compile, the truck project gets affected
> and maven does not build.
>
> Can anyone help me with that?
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Independent Subprojects in Maven

[Ashley Hurkoo]

I am trying sub project to my main project. For example, I have a rental
project(main) and I want to add a truck project and a car project which are
independent of the Main project. The problem I am having is when I build
maven and the car project does not compile, the truck project gets affected
and maven does not build.

Can anyone help me with that?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] - maven-release-plugin cannot load SCM provider

[Trent Rosenbaum]

This is the feedback I got from running mvn release:prepare

[INFO] [release:prepare]
[INFO] What tag name should be used?
0.1.2
[INFO] Tagging release with the label 0.1.2.
Provider message:
The svn tag command failed.
Command output:
svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
s\my_repo\bug-control-model\tags\0.1.2'

[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] An error is occurred in the tag process.


The URL for the tagBase is identical to the URL supplied within the
developerConnection element but "tags" replaces "trunk".

Trent


On 08/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> The bug is for the default of ../tags when used instead of a tagbase
> as you have, so it is different.
>
> Above that exception, there should have been output from the svn
> command. Does that reveal anything?
>
> - Brett
>
> On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > I did not have this pom.xml checked  into SVN and so it was trying to
> > work with the previous revision of my file and this did not have a SCM
> > URL defined.  I have been able to get the plugin to prompt me for
> > input regarding the tags, but I am falling over in the tagging process
> > with the following exception:
> >
> > Is this the same exception that has lead to the creation of the
> > following issue in jira?
> >
> > http://jira.codehaus.org/browse/MNG-883
> >
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: An error is 
> > occurred in
> > the tag process.
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is 
> > occurred
> > in the tag process.
> > at 
> > org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > eReleaseMojo.java:1414)
> > at 
> > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > leaseMojo.java:246)
> >
> >
> > thanks for taking to time to look into this.
> > Trent
> >
> > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > I thought I had used windows paths in the SCM URL before without
> > > issues, but its worth trying:
> > >
> > > scm|svn|file:///d:/subversion...
> > >
> > > hth,
> > > Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > This is the SCM URL for the project:
> > > >
> > > > 
> > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> > > > 
> > > >
> > > > and the plugin is configured with the following tagbase element:
> > > >
> > > > 
> > > > org.apache.maven.plugins
> > > > maven-release-plugin
> > > > 2.0-beta-3
> > > > 
> > > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags
> > > > 
> > > > 
> > > >
> > > >
> > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > > They both use the same library - so the release plugin is for
> > > > > automating release related tasks, the scm plugin for development
> > > > > related tasks.
> > > > >
> > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > there is still something wrong with it.
> > > > >
> > > > > - Brett
> > > > >
> > > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > > > Thanks for the reply.
> > > > > > When I started to use the plugin I was prefixing the URLs with
> > > > > > "scm:svn", but then I still had a problem so thought about exploring
> > > > > > and that is why I asked about setting the scm provider in a 
> > > > > > different
> > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 
> > > > > > of the plugin.
> > > > > >
> > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > plugin is planned to allow developers to aquire a project without a
> > > > > > pom.xml and then to complete the every day version control tasks?
> > > > > > With this in mind is it best to view the maven-release plugin as a
> > > > > > component that should be used to release code for a repository 
> > > > > > instead
> > > > > > of completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > know the thoughts behind each plugin.
> > > > > >
> > > > > > - Maven output -
> > > > > >
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO] 
> > > > > > ---
> > > > > > [INFO] An error is occurred in the status process.
> > > > > >
> > > > > > Embedded error: Can't load the scm provider.
> > > > > > The scm url is invalid.
> > > > > >
> > > > > > - stack trace --
> > > > > >
> > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm 
> > > > > > provider.
> > > > > > at 
> > > > > > org.a

Re: [M2] - maven-release-plugin cannot load SCM provider

[Brett Porter]

The bug is for the default of ../tags when used instead of a tagbase
as you have, so it is different.

Above that exception, there should have been output from the svn
command. Does that reveal anything?

- Brett

On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> I did not have this pom.xml checked  into SVN and so it was trying to
> work with the previous revision of my file and this did not have a SCM
> URL defined.  I have been able to get the plugin to prompt me for
> input regarding the tags, but I am falling over in the tagging process
> with the following exception:
>
> Is this the same exception that has lead to the creation of the
> following issue in jira?
>
> http://jira.codehaus.org/browse/MNG-883
>
>
> org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred 
> in
> the tag process.
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error is 
> occurred
> in the tag process.
> at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> eReleaseMojo.java:1414)
> at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> leaseMojo.java:246)
>
>
> thanks for taking to time to look into this.
> Trent
>
> On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > I thought I had used windows paths in the SCM URL before without
> > issues, but its worth trying:
> >
> > scm|svn|file:///d:/subversion...
> >
> > hth,
> > Brett
> >
> > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > This is the SCM URL for the project:
> > >
> > > 
> > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> > > 
> > >
> > > and the plugin is configured with the following tagbase element:
> > >
> > > 
> > > org.apache.maven.plugins
> > > maven-release-plugin
> > > 2.0-beta-3
> > > 
> > > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags
> > > 
> > > 
> > >
> > >
> > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > They both use the same library - so the release plugin is for
> > > > automating release related tasks, the scm plugin for development
> > > > related tasks.
> > > >
> > > > Can you please repost the full SCM URL that gave you this error -
> > > > there is still something wrong with it.
> > > >
> > > > - Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > > Thanks for the reply.
> > > > > When I started to use the plugin I was prefixing the URLs with
> > > > > "scm:svn", but then I still had a problem so thought about exploring
> > > > > and that is why I asked about setting the scm provider in a different
> > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of 
> > > > > the plugin.
> > > > >
> > > > > During my reading of the site I noticed that both the scm and the
> > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > plugin is planned to allow developers to aquire a project without a
> > > > > pom.xml and then to complete the every day version control tasks?
> > > > > With this in mind is it best to view the maven-release plugin as a
> > > > > component that should be used to release code for a repository instead
> > > > > of completing a checkout/checkin, copy etc manually?  I just want to
> > > > > know the thoughts behind each plugin.
> > > > >
> > > > > - Maven output -
> > > > >
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO] 
> > > > > ---
> > > > > [INFO] An error is occurred in the status process.
> > > > >
> > > > > Embedded error: Can't load the scm provider.
> > > > > The scm url is invalid.
> > > > >
> > > > > - stack trace --
> > > > >
> > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm 
> > > > > provider.
> > > > > at 
> > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > cmHelper.java:104)
> > > > > at 
> > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > r.java:169)
> > > > > at 
> > > > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > fications(PrepareReleaseMojo.java:510)
> > > > > ... 19 more
> > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: 
> > > > > The scm url i
> > > > > s invalid.
> > > > > at 
> > > > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > itory(SvnScmProvider.java:84)
> > > > > at 
> > > > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > ry(DefaultScmManager.java:126)
> > > > > at 
> > > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > cmHelper.java:82)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 07/11/05, Brett Porter <[EMAIL

Re: [M2] - maven-release-plugin cannot load SCM provider

[Trent Rosenbaum]

I did not have this pom.xml checked  into SVN and so it was trying to
work with the previous revision of my file and this did not have a SCM
URL defined.  I have been able to get the plugin to prompt me for
input regarding the tags, but I am falling over in the tagging process
with the following exception:

Is this the same exception that has lead to the creation of the
following issue in jira?

http://jira.codehaus.org/browse/MNG-883


org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
the tag process.

Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
in the tag process.
at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
eReleaseMojo.java:1414)
at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
leaseMojo.java:246)


thanks for taking to time to look into this.
Trent

On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> I thought I had used windows paths in the SCM URL before without
> issues, but its worth trying:
>
> scm|svn|file:///d:/subversion...
>
> hth,
> Brett
>
> On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > This is the SCM URL for the project:
> >
> > 
> > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> > 
> >
> > and the plugin is configured with the following tagbase element:
> >
> > 
> > org.apache.maven.plugins
> > maven-release-plugin
> > 2.0-beta-3
> > 
> > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags
> > 
> > 
> >
> >
> > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > They both use the same library - so the release plugin is for
> > > automating release related tasks, the scm plugin for development
> > > related tasks.
> > >
> > > Can you please repost the full SCM URL that gave you this error -
> > > there is still something wrong with it.
> > >
> > > - Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > Thanks for the reply.
> > > > When I started to use the plugin I was prefixing the URLs with
> > > > "scm:svn", but then I still had a problem so thought about exploring
> > > > and that is why I asked about setting the scm provider in a different
> > > > manner.  I have again used these prefixes and I still get a problem.
> > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of 
> > > > the plugin.
> > > >
> > > > During my reading of the site I noticed that both the scm and the
> > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > plugin is planned to allow developers to aquire a project without a
> > > > pom.xml and then to complete the every day version control tasks?
> > > > With this in mind is it best to view the maven-release plugin as a
> > > > component that should be used to release code for a repository instead
> > > > of completing a checkout/checkin, copy etc manually?  I just want to
> > > > know the thoughts behind each plugin.
> > > >
> > > > - Maven output -
> > > >
> > > > [ERROR] BUILD ERROR
> > > > [INFO] 
> > > > ---
> > > > [INFO] An error is occurred in the status process.
> > > >
> > > > Embedded error: Can't load the scm provider.
> > > > The scm url is invalid.
> > > >
> > > > - stack trace --
> > > >
> > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm 
> > > > provider.
> > > > at 
> > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > cmHelper.java:104)
> > > > at 
> > > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > r.java:169)
> > > > at 
> > > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > fications(PrepareReleaseMojo.java:510)
> > > > ... 19 more
> > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The 
> > > > scm url i
> > > > s invalid.
> > > > at 
> > > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > itory(SvnScmProvider.java:84)
> > > > at 
> > > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > ry(DefaultScmManager.java:126)
> > > > at 
> > > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > cmHelper.java:82)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > > Your SCM URL should start:
> > > > >
> > > > > scm:svn:file://...
> > > > >
> > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > in the second argument above.
> > > > >
> > > > > - Brett
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > -

Re: [MAVEN 2] Update /maven.apache.org/guides/introduction/introduction-to-repositories.html

[Jerarckill - ANS]

Ah good, I didn't know this!  This is something interesting to know indeed.

Thanks for the precision, i'll go have a look

Jer

On Mon, 07 Nov 2005 14:26:06 +0100, Jeff Jensen  
<[EMAIL PROTECTED]> wrote:



Regarding the wiki/others helping, do you know that the code and docs are
available to you from subversion?  When having something to contribute,  
you

can get it and patch it.  I have done this many times on m1.1, and was an
easy process.  The "hardest" part was waiting for a committer to get the
patch into svn.  This usually only took up to 2 days, but did take about  
2

weeks a couple of times.

-Original Message-
From: Jadoulle Jérôme [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 2:28 AM
To: users@maven.apache.org
Subject: [MAVEN 2] Update
/maven.apache.org/guides/introduction/introduction-to-repositories.html

Hello,


I am trying to set-up an in-house remote repository for my company.


We did this already in the past using maven 1.02 (though I wasn't the  
guy in

charge) and we now want to move to V2.0.


Problem is that documentation about how to do this in a generic fashion  
(I
don't want the connection information to be written in each POM.xml  
file) is
still referring to Maven 1.0 "build.properties" file... Which doesn't  
help

me.

So, I would be grateful to you to have this introduction to repositories  
to

be updated to match the V2 and it's Settings.xml file.


In fact, I think it would help a lot of people to have:

-  XSD schema sort of reference pages about each XML file users  
are

likely to change (settings.xml, pom.xml,...).

-  More precise documentation for "basic examples".  I personally
think that, in the current state, you rely too much on user's knowledge,
which is, when he starts to use maven for the first, quite limitated.


I am certainly not saying that you are making a bad job, not at all.  I  
am
just telling that I would have a far better Maven experience if more  
precise

documentation was made available to users.  Reference pages are very
important, I think.


A last note: I bet that part of your answer will tell that you prefer  
focus

on correcting bugs and bring more functionality to the community and that
you are already doing all what you can concerning the documentation. And
you'll be right!  But did you think about putting documentation in a  
wiki or

something, where all willing-to-help users would be able to make the
knowledge base grow and correct documentation errors, imperfections,... ?
Perhaps this would be a very interesting thing to do.  What do you think  
of

it?


Anyway, thank you very much for at least having read this mail,


Jérôme JADOULLE



**
This email and any files transmitted with it are confidential and  
intended
solely for the use of the individual or entity to whom they are  
addressed.
If you have received this email in error please notify the system  
manager.

Rijksdienst voor Pensioenen
Office National des Pensions

**



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Blocking Access to ibiblio, etc...

[Brian E. Fox]

I see. You could do this to define a new repo:

 
  default


my-repo
http://x

true


true



 



default


 As far as changing the super pom, you can redefine anything you don't
like. You should be able to redefine central and set both snapshots and
releases to false.

Checkout the projecthelp:effective-settings and
projecthelp:effective-pom for output of the settings and poms after
processing.

-Original Message-
From: Duane Homick [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 07, 2005 7:02 PM
To: Maven Users List
Subject: RE: Blocking Access to ibiblio, etc...

Doing this has changed where central looks for the files, however, it
doesnt change any of the information about "central".

Downloading:
file:///Z:/sw/repository/master//junit/junit/3.8.1/junit-3.8.1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org
/maven2)
[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java [INFO] Extractor for
language: java found 2 mojo descriptors.
[INFO] Applying extractor for language: bsh [INFO] Extractor for
language: bsh found 0 mojo descriptors.
Downloading:
file:///Z:/sw/repository/master//junit/junit/3.8.1/junit-3.8.1.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org
/maven2)
[INFO]

-
---
[ERROR] BUILD ERROR
[INFO]

-
---
[INFO] Failed to resolve artifact.

GroupId: junit
ArtifactId: junit
Version: 3.8.1

Reason: Unable to download the artifact from any repository
  junit:junit:3.8.1:jar

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)


You see above that it still says things are coming from central and
snapshots at the maven urls.  Is there a way to have these become my
urls?

Also, is there a way to change the Super POM or are the settings in it
just something I will have to live with?

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 6:13 PM
To: Maven Users List
Subject: RE: Blocking Access to ibiblio, etc...


Create a mirror of "central" and either point it to your internal repo
or to someplace not ibiblio. 

-Original Message-
From: Duane Homick [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 5:53 PM
To: users@maven.apache.org
Subject: Blocking Access to ibiblio, etc...

Is there an easy way to block access to remote repositories such that
only our corporate repository and a developer's local repository will be
used to resolve dependencies?  If neither are found, then the dependency
would fail to be resolved.

Thanks
Duane Homick
Software Engineer
Sandvine Incorporated

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Blocking Access to ibiblio, etc...

[Duane Homick]

Doing this has changed where central looks for the files, however, it doesnt 
change any of the information about "central".

Downloading: file:///Z:/sw/repository/master//junit/junit/3.8.1/junit-3.8.1.pom
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 2 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
Downloading: file:///Z:/sw/repository/master//junit/junit/3.8.1/junit-3.8.1.jar
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Failed to resolve artifact.

GroupId: junit
ArtifactId: junit
Version: 3.8.1

Reason: Unable to download the artifact from any repository
  junit:junit:3.8.1:jar

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)


You see above that it still says things are coming from central and snapshots 
at the maven urls.  Is there a way to have these become my urls?

Also, is there a way to change the Super POM or are the settings in it just 
something I will have to live with?

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 6:13 PM
To: Maven Users List
Subject: RE: Blocking Access to ibiblio, etc...


Create a mirror of "central" and either point it to your internal repo
or to someplace not ibiblio. 

-Original Message-
From: Duane Homick [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 07, 2005 5:53 PM
To: users@maven.apache.org
Subject: Blocking Access to ibiblio, etc...

Is there an easy way to block access to remote repositories such that
only our corporate repository and a developer's local repository will be
used to resolve dependencies?  If neither are found, then the dependency
would fail to be resolved.

Thanks
Duane Homick
Software Engineer
Sandvine Incorporated

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JarJar missing...

[Carlos Sanchez]

Done. All versions however are under the groupId com.tonicsystems


On 11/5/05, Guillaume Laforge <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The Groovy project uses jarjar in its M1 build, and we recently
> noticed that jarjar-0.5.jar is missing from the ibiblio repository.
>
> There used to be a tonic folder containing the version 0.5.
> And now, there's only a jarjar folder containing and old 0.2 version.
>
> Could jarjar-0.5.jar be back in the M1 repository please?
>
> Thanks in advance,
>
> --
> Guillaume Laforge
> Groovy Project Manager
> http://glaforge.free.fr/blog/groovy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] ant bug with EnumeratedAttribute task parameters=

[Brett Porter]

Did you run "mvn clean install" to install it?

- Brett

On 11/8/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> hi again,
>
>im trying to debug the problem below (hoping i can find a
> workaround) but since policy prevents me from installing subversion in
> my workstation (even if it doesnt entail a real installer), i just
> manually retrieved the maven-antrun-plugin from
> http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-antrun-plugin/
>
>   i am pretty sure that i have copied the correct structure (sans the
> site directory) and the latest versions of each source/resource
> file[1]. i edited the pom and based it on the pom included in the
> original antrun plugin jar file. my project pom looks like this
>
>   org.apache.maven.plugins
>   maven-antrun-plugin
>   maven-plugin
>   Maven AntRun Plugin
>   1.0
>
>   
> 
>   org.apache.maven
>   maven-plugin-tools-api
>   2.0
> 
> 
>   ant
>   ant
>   1.6.2
> 
>
>   
>
>
> i just inserted some printout statements to help get an idea how
> things are done (my java skills need some more work). the 'impromptu'
> project compiles and installs fine in my local repository but using
> the plugin causes this error:
>
> 
> [ERROR] Nonexistent component:
> org.codehaus.plexus.component.configurator.ComponentConfiguratoroverride
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run': Unable to find
> the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the
> plugin 'org.apache.maven.plugins:maven-antrun-plugin'
>
> Component descriptor cannot be found in the component repository:
> org.codehaus.plexus.component.configurator.ComponentConfigu
> ratoroverride.
> ==
>
> i noticed that the original plugin jar file has the
> META-INF/plexus/component.xml and META-INF/maven/plugin.xml. My
> 'hijacked'  antrun plugin does no thave these files. can you point to
> me what i missed? thanks.
>
>
> [1] dir /s /b /a-d antrun\src
> src\main\java\org\apache\maven\plugin\antrun\AbstractAntMojo.java
> src\main\java\org\apache\maven\plugin\antrun\AntPropertyHelper.java
> src\main\java\org\apache\maven\plugin\antrun\AntRunMojo.java
> src\main\java\org\apache\maven\plugin\antrun\components\AntTargetConverter.java
> src\resources\META-INF\plexus\components.xml
>
> ciao!
>
>
> On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > hi,
> >
> >  the attachments caused my mail to bounce so you can access the files
> > using this link (combined to a single file, 8KB in total) :
> >
> >http://ramfree17.org/hasty/maven/antrun_issue.zip
> >
> >
> > ciao!
> >
> > On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > > hi,
> > >
> > >  the ant-run plugin (or the launcher) seems unable to properly
> > > convert attributes that are of the type EnumeratedAttribute[1]. the
> > > execution always fail with an error that the attribute being set is
> > > not supported by the class.
> > >
> > >  i have attached 3 files to serve as a test case for this.
> > >
> > >  1. "sample.zip" - contains the project that will serve as the main
> > > test case. it really is just the plugin tutorial and i just added the
> > > followign in the pom.xml so my test Task will be called during compile
> > > time:
> > >
> > > 
> > >   
> > >
> > >testbed
> > >tests
> > >1.0
> > >
> > >
> > >ant
> > >ant
> > >1.5
> > >
> > >   
> > >  
> > > 
> > >maven-antrun-plugin
> > >
> > >   
> > >  compile
> > > 
> > >
> > >> >   target = "test-run"
> > >   antfile = "${basedir}/build.xml">
> > >
> > >> > value="FirstValue"/>
> > >
> > >
> > > 
> > > 
> > >run
> > >  
> > >
> > > 
> > >  
> > >   
> > > 
> > >
> > >   2. "testbed.zip" - contains the test Ant Task jar file. the test
> > > Task has one attribute that is derived from EnumeratedAttribute.
> > >
> > >   3.  "testbed-src.zip" - contains the source code for the testbed
> > > artifact (in case somebody is interested).
> > >
> > >
> > >   i think the problem is just with the launcher since the task runs
> > > fairly well from normal Ant invocation. i found this problem when i
> > > was trying to use the  task in the ant-optinoal package.
> > > anybody have an idea how to work around this?
> > >
> > >   thanks.
> > >
> > > [1] http://ant.apache.org/manual/develop

Re: [M2] - maven-release-plugin cannot load SCM provider

[Brett Porter]

I thought I had used windows paths in the SCM URL before without
issues, but its worth trying:

scm|svn|file:///d:/subversion...

hth,
Brett

On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> This is the SCM URL for the project:
>
> 
> scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> 
>
> and the plugin is configured with the following tagbase element:
>
> 
> org.apache.maven.plugins
> maven-release-plugin
> 2.0-beta-3
> 
> scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags
> 
> 
>
>
> On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > They both use the same library - so the release plugin is for
> > automating release related tasks, the scm plugin for development
> > related tasks.
> >
> > Can you please repost the full SCM URL that gave you this error -
> > there is still something wrong with it.
> >
> > - Brett
> >
> > On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > Thanks for the reply.
> > > When I started to use the plugin I was prefixing the URLs with
> > > "scm:svn", but then I still had a problem so thought about exploring
> > > and that is why I asked about setting the scm provider in a different
> > > manner.  I have again used these prefixes and I still get a problem.
> > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the 
> > > plugin.
> > >
> > > During my reading of the site I noticed that both the scm and the
> > > release plugin are similar.  Is it right to think that the maven-scm
> > > plugin is planned to allow developers to aquire a project without a
> > > pom.xml and then to complete the every day version control tasks?
> > > With this in mind is it best to view the maven-release plugin as a
> > > component that should be used to release code for a repository instead
> > > of completing a checkout/checkin, copy etc manually?  I just want to
> > > know the thoughts behind each plugin.
> > >
> > > - Maven output -
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO] 
> > > ---
> > > [INFO] An error is occurred in the status process.
> > >
> > > Embedded error: Can't load the scm provider.
> > > The scm url is invalid.
> > >
> > > - stack trace --
> > >
> > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > at 
> > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > cmHelper.java:104)
> > > at 
> > > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > r.java:169)
> > > at 
> > > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > fications(PrepareReleaseMojo.java:510)
> > > ... 19 more
> > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The 
> > > scm url i
> > > s invalid.
> > > at 
> > > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > itory(SvnScmProvider.java:84)
> > > at 
> > > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > ry(DefaultScmManager.java:126)
> > > at 
> > > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > cmHelper.java:82)
> > >
> > >
> > >
> > >
> > >
> > > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > > Your SCM URL should start:
> > > >
> > > > scm:svn:file://...
> > > >
> > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > in the second argument above.
> > > >
> > > > - Brett
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Using Maven as Eclipse class-path container

[Brett Porter]

On 11/8/05, Michael Böckling <[EMAIL PROTECTED]> wrote:
> Are there any informations about this topic? Maybe the soon-to-be
> released M2 Eclipse plugin
> (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this?

Correct, and more.

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] - maven-release-plugin cannot load SCM provider

[Trent Rosenbaum]

This is the SCM URL for the project:


scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk


and the plugin is configured with the following tagbase element:


org.apache.maven.plugins
maven-release-plugin
2.0-beta-3

scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags




On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> They both use the same library - so the release plugin is for
> automating release related tasks, the scm plugin for development
> related tasks.
>
> Can you please repost the full SCM URL that gave you this error -
> there is still something wrong with it.
>
> - Brett
>
> On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > Thanks for the reply.
> > When I started to use the plugin I was prefixing the URLs with
> > "scm:svn", but then I still had a problem so thought about exploring
> > and that is why I asked about setting the scm provider in a different
> > manner.  I have again used these prefixes and I still get a problem.
> > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the 
> > plugin.
> >
> > During my reading of the site I noticed that both the scm and the
> > release plugin are similar.  Is it right to think that the maven-scm
> > plugin is planned to allow developers to aquire a project without a
> > pom.xml and then to complete the every day version control tasks?
> > With this in mind is it best to view the maven-release plugin as a
> > component that should be used to release code for a repository instead
> > of completing a checkout/checkin, copy etc manually?  I just want to
> > know the thoughts behind each plugin.
> >
> > - Maven output -
> >
> > [ERROR] BUILD ERROR
> > [INFO] 
> > ---
> > [INFO] An error is occurred in the status process.
> >
> > Embedded error: Can't load the scm provider.
> > The scm url is invalid.
> >
> > - stack trace --
> >
> > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > at 
> > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > cmHelper.java:104)
> > at 
> > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > r.java:169)
> > at 
> > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > fications(PrepareReleaseMojo.java:510)
> > ... 19 more
> > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm 
> > url i
> > s invalid.
> > at 
> > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > itory(SvnScmProvider.java:84)
> > at 
> > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > ry(DefaultScmManager.java:126)
> > at 
> > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > cmHelper.java:82)
> >
> >
> >
> >
> >
> > On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > > Your SCM URL should start:
> > >
> > > scm:svn:file://...
> > >
> > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > in the second argument above.
> > >
> > > - Brett
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Issue tracking system

[Brett Porter]

Currently we have the following integration:
- project info reports list the issue tracker (supports jira, bugzilla
and scarab I believe)
- changes plugin can retrieve changes from jira

What type of support are you looking for?

- Brett

On 11/8/05, Srepfler Srgjan <[EMAIL PROTECTED]> wrote:
> Is there a way to integrate maven with an issue tracking system such as
> Trac?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] install plugin bug with classifiers ?

[Brett Porter]

I see. Because the configuration for debugging is at the compilation
phase which is not called a second time.

Let's step back. Which do you want to achieve:
- be able to run with a profile that generates and installs a nodebug
jar instead, or,
- generate and install both jars each time.

Cheers,
Brett

On 11/8/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 07, 2005 at 01:19:11PM +, Brett Porter wrote:
> > Sorry, what option are you referring to?
>
> I'm sorry if I was not clear.
> Basically, I'd like to produce a jar with debug info
> and a jar without debug info (for a very size constrained environment).
>
> So I have a profile (nodebug), where I configure the fact that debug
> should be disabled.
>
> By taking the example maven-model as you suggested, M2 produces two
> jars, each of them without debug info:
> - somejar-1.0.jar
> - somejar-1.0-nodebug.jar
>
> My only small issue remaining is that when I ask M2 to perform an "install",
> both jars are installed and the jar with debug info (installed with
> the standard profile) is replaced by the jar without debug info by the
> same name.
>
> --
> Julien
>
> > Configuration inside the execution will be restricted to that execution.
> >
> > - Brett
> >
> > On 11/7/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > On Mon, Nov 07, 2005 at 10:10:58AM +1100, Brett Porter wrote:
> > > > Take a look at maven-model in the Maven sources. It does exactly this,
> > > > and last time I checked it worked :)
> > >
> > > Getting closer... :)
> > >
> > > I was doing:
> > >
> > > 
> > >   nodebug
> > > 
> > > 
> > >   
> > > package
> > > 
> > >   jar
> > > 
> > >   
> > > 
> > >
> > > which failed as I described, and when I change it to:
> > >
> > > 
> > >   
> > > package
> > > 
> > >   jar
> > > 
> > > 
> > >   nodebug
> > > 
> > >   
> > > 
> > >
> > > the build does not fail anymore.
> > >
> > > However, it produces two jars:
> > > - somejar-1.0.jar
> > > - somejar-1.0-nodebug.jar
> > >
> > > but it applies the option from the profile to BOTH jars.
> > > I would like it either to produce a single jar, or to produce two
> > > of them, but without applying the profile rules to both jars !
> > >
> > > Thanks.
> > >
> > > --
> > > Julien Stern
> > >
> > > >
> > > > - Brett
> > > >
> > > > On 11/4/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > On Fri, Nov 04, 2005 at 09:22:25AM +1100, Brett Porter wrote:
> > > > > > I think you need:
> > > > > >
> > > > > > package
> > > > > >
> > > > > > and
> > > > > >
> > > > > > 
> > > > > >   jar
> > > > > > 
> > > > > >
> > > > > > in the jar plugin as it is not being run otherwise.
> > > > > >
> > > > > > - Brett
> > > > >
> > > > > No luck with this either unfortunately.
> > > > > I still have:
> > > > >
> > > > > [INFO] [jar:jar]
> > > > > [INFO] Building jar:
> > > > > /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar
> > > > > [INFO] [install:install]
> > > > > [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to
> > > > > /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar
> > > > >
> > > > > I guess I'll file a bug report :)
> > > > > Thanks for your help.
> > > > >
> > > > > --
> > > > > Julien
> > > > >
> > > > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > > > On Thu, Nov 03, 2005 at 10:05:50AM +1100, Brett Porter wrote:
> > > > > > > > How are you calling it?
> > > > > > > >
> > > > > > > > Sounds like you are running install:install over a multiproject 
> > > > > > > > -
> > > > > > > > instead you should use "install".
> > > > > > >
> > > > > > > Well, I believe I'm doing something fairly standard.
> > > > > > > I'm calling:
> > > > > > >
> > > > > > > $ mvn -Pnodebug install
> > > > > > > or
> > > > > > > $ mvn -Pnodebug clean install
> > > > > > >
> > > > > > > With "nodebug" containing:
> > > > > > >
> > > > > > >   
> > > > > > > 
> > > > > > >   
> > > > > > > true
> > > > > > > org.apache.maven.plugins
> > > > > > > maven-compiler-plugin
> > > > > > > 
> > > > > > >   true
> > > > > > >   false
> > > > > > >   true
> > > > > > >   
> > > > > > > 
> > > > > > >   
> > > > > > > 
> > > > > > >   
> > > > > > >   
> > > > > > > true
> > > > > > > org.apache.maven.plugins
> > > > > > > maven-jar-plugin
> > > > > > > 
> > > > > > >   nodebug
> > > > > > > 
> > > > > > >   
> > > > > > > 
> > > > > > >   
> > > > > > >
> > > > > > > There are two levels of POM inheritance if that may also 
> > > > > > > diagnose...
> > > > > > >
> > > > > > > By the way, thanks a lot for your answers to my other emails,
> > > > > > > I'll try to find time to add improv

Issue tracking system

[Srepfler Srgjan]

Is there a way to integrate maven with an issue tracking system such as 
Trac?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Blocking Access to ibiblio, etc...

[Brian E. Fox]

Create a mirror of "central" and either point it to your internal repo
or to someplace not ibiblio. 

-Original Message-
From: Duane Homick [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 07, 2005 5:53 PM
To: users@maven.apache.org
Subject: Blocking Access to ibiblio, etc...

Is there an easy way to block access to remote repositories such that
only our corporate repository and a developer's local repository will be
used to resolve dependencies?  If neither are found, then the dependency
would fail to be resolved.

Thanks
Duane Homick
Software Engineer
Sandvine Incorporated

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] dependency license management

[Brett Porter]

On 11/8/05, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> IMHO it could be a first step to add a License column in the Project
> Dependencies report.

We need to do something about this report. It's awfully cluttered
(perhaps just trimming the description a bit would be helpful?)

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Sejo Cesic is out of the office.

[Sejo . Cesic]

I will be out of the office starting Tue 11/08/2005 and will not return
until Wed 11/16/2005.

I will respond to your message when I return.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [M2] dependency license management

[Vincent Siveton]

Hi

> The information is there (the POM can add it), and its a requirement
> on new POMs added to the repository by manual upload, though I'm sure

+1 for this feature

> there are quite a few gaps in the repository which we'd need to fill
> once this is analysed.
> 
> At present, this is something we are interested in working on, but
> don't have any immediate plans to implement. It would be fairly
> similar to the dependencies report.

IMHO it could be a first step to add a License column in the Project
Dependencies report.

Cheers,

Vincent



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Blocking Access to ibiblio, etc...

[Duane Homick]

Is there an easy way to block access to remote repositories such that only our 
corporate repository and a developer's local repository will be used to resolve 
dependencies?  If neither are found, then the dependency would fail to be 
resolved.

Thanks
Duane Homick
Software Engineer
Sandvine Incorporated

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] dependency license management

[Brett Porter]

The information is there (the POM can add it), and its a requirement
on new POMs added to the repository by manual upload, though I'm sure
there are quite a few gaps in the repository which we'd need to fill
once this is analysed.

At present, this is something we are interested in working on, but
don't have any immediate plans to implement. It would be fairly
similar to the dependencies report.

Regards,
Brett

On 11/8/05, Ruel Loehr <[EMAIL PROTECTED]> wrote:
> We have a ginourmous number thirdparty dependencies.   One of the things
> we need to accomplish is to keep track of the licenses that are
> associated with the thirdparty dependencies to avoid any legal issues.
>
> I was looking into the project-info-reports plugin, which, btw, makes my
> heart flutter.  It's very cool, but doesn't look like something that
> supports thirdparty licenses.
>
> Question:
> 1)  Do any thirdparty lib license management plugins already exist?
> 2)  If not, are there any plans on the books to do so?
>
> I am basically looking for sometype of report which summarizes the
> spectrum of licenses used, and which dependencies use them.   This may
> be a plugin I need to write.
>
>
>
> Ruel Loehr
> JBoss QA
>
> -
> 512-626-2782
> Yahoo: ruelloehr
> Skype: ruelloehr
> AOL: dokoruel
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[M2] dependency license management

[Ruel Loehr]

We have a ginourmous number thirdparty dependencies.   One of the things
we need to accomplish is to keep track of the licenses that are
associated with the thirdparty dependencies to avoid any legal issues.

I was looking into the project-info-reports plugin, which, btw, makes my
heart flutter.  It's very cool, but doesn't look like something that
supports thirdparty licenses.

Question:
1)  Do any thirdparty lib license management plugins already exist?
2)  If not, are there any plans on the books to do so?

I am basically looking for sometype of report which summarizes the
spectrum of licenses used, and which dependencies use them.   This may
be a plugin I need to write.

  

Ruel Loehr
JBoss QA
 
-
512-626-2782
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] - maven-release-plugin cannot load SCM provider

[Brett Porter]

They both use the same library - so the release plugin is for
automating release related tasks, the scm plugin for development
related tasks.

Can you please repost the full SCM URL that gave you this error -
there is still something wrong with it.

- Brett

On 11/8/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> Thanks for the reply.
> When I started to use the plugin I was prefixing the URLs with
> "scm:svn", but then I still had a problem so thought about exploring
> and that is why I asked about setting the scm provider in a different
> manner.  I have again used these prefixes and I still get a problem.
> Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the 
> plugin.
>
> During my reading of the site I noticed that both the scm and the
> release plugin are similar.  Is it right to think that the maven-scm
> plugin is planned to allow developers to aquire a project without a
> pom.xml and then to complete the every day version control tasks?
> With this in mind is it best to view the maven-release plugin as a
> component that should be used to release code for a repository instead
> of completing a checkout/checkin, copy etc manually?  I just want to
> know the thoughts behind each plugin.
>
> - Maven output -
>
> [ERROR] BUILD ERROR
> [INFO] 
> ---
> [INFO] An error is occurred in the status process.
>
> Embedded error: Can't load the scm provider.
> The scm url is invalid.
>
> - stack trace --
>
> Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> at 
> org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> cmHelper.java:104)
> at 
> org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> r.java:169)
> at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> fications(PrepareReleaseMojo.java:510)
> ... 19 more
> Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm 
> url i
> s invalid.
> at 
> org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> itory(SvnScmProvider.java:84)
> at 
> org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> ry(DefaultScmManager.java:126)
> at 
> org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> cmHelper.java:82)
>
>
>
>
>
> On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > Your SCM URL should start:
> >
> > scm:svn:file://...
> >
> > Maven has no knowledge of the SVN protocols, just the scm type given
> > in the second argument above.
> >
> > - Brett
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can't use maven2 (offline)

[Brett Porter]

Offline actually avoids all remote repositories (even file ones, as
they might be on a shared drive).

- Brett

On 11/8/05, Eric Parpal <[EMAIL PROTECTED]> wrote:
> I tried with offline=false and file:///mypath/ibiblio/maven2 (in
> settings.xml and in the command line).
> Always the same message.
>
> >Finally, are you sure you got all the dependencies of the archetype plugin
> >and the archetype artifact itself?
> No I am not sure because no message warns me.
> The character '*' meaning that all subfiles and subdirectories have been
> downloaded, the content of my /mypath/ibiblio/maven2 directory is :
> /mypath/ibiblio/maven2/org/apache/maven/archetypes/*
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-archetype-plugin/*
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-install-plugin/*
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/index.html
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml.md5
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml.sha1
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/plugins.xml.md5
> /mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/plugins.xml.sha1
> /mypath/ibiblio/maven2/org/apache/maven/plugins/maven-archetype-plugin/*
> /mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml
> /mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml.md5
> /mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml.sha1
>
> NB : I don't know the difference between org/apache/maven/plugins and
> plugins/org/apache/maven, I took both
>
>
> >If you are sure you have all the dependencies, and that your repository
> >path is correct, you can try the fully specified invocation, which looks
> >like: mvn :::
> I'm sure of nothing. I used url=file:///mypath/ibiblio/maven2. Is it right ?
> (I supposed that this path should stop at the directory "maven2", as the
> "internet" one does : http://www.ibiblio.org/maven2).
> Do I have to define it as a "pluginRepository" or as a "repository" ? (In
> doubt, I did both)
> Then, I tried mvn
> org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-3:create -D... and
> gets another message (thanks for this!) :
> "Downloading
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.pom";
> ... Error getting pom ... from the specified remote repositories: central
> (http://repo1.maven.org/maven2)"
> So, I can't see mention of my repository. I don't know why. I might have
> missed something.
> Besides, when I look for this file in the internet repository, I can't find
> it.
> Any help or suggestion will be welcomed.
> Thanks.
>
> _
> Une chance par jour de gagner un voyage au soleil avec Magic Search !
> http://www.magicsearch.fr
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Don't fail build when tests fail during site/site-deploy steps

[Erick Dovale]

Is this in jira already?? I could not find it.

edovale.

Brett Porter wrote:


This is a bug that will be fixed so it isn't required.

- Brett

On 11/4/05, Arnd Brusdeilins <[EMAIL PROTECTED]> wrote:
 


|maven -Dmaven.test.failure.ignore=true site
should do this
|
Duane Homick wrote:
   


Is there a way to configure the site-deploy for use with surefire-reports such 
that if the junit tests that are run fail, they dont fail the build and cause 
the site not to be distributed?  Otherwise, what is the point of the surefire 
reports since it could only possibly ever show results with 100% success.

Thanks
Duane Homick

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Unit test stub object question

[Arnaud Bailly]

Aaron Colwell wrote:

Hi,


Hello,
Could'n you make a separate 'test-stub' project and add a dependency in 
your project ? This would cleanly separate test code from main code 
while giving you greater control on how your stub code is structured.


Yours,

PS: I have heard that maven 2.0 gives you a notion of context for 
dependencies and artifacts that seems to solve this kind of issue.



--
Arnaud Bailly - Ingénieur de Recherche
NORSYS
1, rue de la Cense des Raines
ZAC du Moulin
59710 ENNEVELIN
Tel : (33) 3 28 76 56 76
Fax : (33) 3 28 76 57 00
Web : http://www.norsys.fr

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: library dependancy wrong?

[Srepfler Srgjan]

In the end it was the display taglib that was importing the wrong 
standard.jar.


Brian Bonner wrote:


Srepfler, check under:

http://www.ibiblio.org/maven2/javax/servlet/jstl/1.1.2/

Brian
On 10/27/05, Srepfler Srgjan <[EMAIL PROTECTED]> wrote:
 


I've imported a dependency on the JSTL library

 jstl
 jstl
 1.1.2
   
However it seems the standard.jar that gets imported is not the correct
version (1.0.4), could someone else check if this happens to you too?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Unit test stub object question

[Aaron Colwell]

Hi,

I'm using Maven 1.1-beta2 for a project I'm working on. I've split the code
into several projects that I use maven multiproject to build. I'm trying to
figure out the best place to put stub objects for my unit tests. Most of our
stubs go in the src/test/... directory that the unit test is in. I've just
run into the case where one of my subprojects needs a stub from another
project. Basically one project is using an interface from another project and
I want to reuse the stub for that interface. One solution I came up with is
to just put the stubs in the src/main tree so they get added to the project's
jar. The "problem" with this is that I don't really want these objects to
show up in the JavaDoc since they are only intended for unit testing and aren't
intended to be part of the project's API/class hierarchy. The other "problem"
is that by moving them into src/main they no longer live with all the other
unit test code. I like the seperation that Maven creates between test code and
application code. I'd like to maintain that.

Does anyone have any suggestions on how I can keep the stubs in the src/test
tree, but also make them available to unit tests in other sub-projects?

Thanks,

Aaron

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] - maven-release-plugin cannot load SCM provider

[Trent Rosenbaum]

Thanks for the reply.
When I started to use the plugin I was prefixing the URLs with
"scm:svn", but then I still had a problem so thought about exploring
and that is why I asked about setting the scm provider in a different
manner.  I have again used these prefixes and I still get a problem.
Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.

During my reading of the site I noticed that both the scm and the
release plugin are similar.  Is it right to think that the maven-scm
plugin is planned to allow developers to aquire a project without a
pom.xml and then to complete the every day version control tasks? 
With this in mind is it best to view the maven-release plugin as a
component that should be used to release code for a repository instead
of completing a checkout/checkin, copy etc manually?  I just want to
know the thoughts behind each plugin.

- Maven output -

[ERROR] BUILD ERROR
[INFO] 
---
[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
The scm url is invalid.

- stack trace --

Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
cmHelper.java:104)
at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
r.java:169)
at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
fications(PrepareReleaseMojo.java:510)
... 19 more
Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
s invalid.
at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
itory(SvnScmProvider.java:84)
at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
ry(DefaultScmManager.java:126)
at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
cmHelper.java:82)





On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Your SCM URL should start:
>
> scm:svn:file://...
>
> Maven has no knowledge of the SVN protocols, just the scm type given
> in the second argument above.
>
> - Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] JAXB Plugin

[Alexandre Poitras]

Whoops sorry, I red your email too fast. You already know about it.

On 11/7/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> This plugin uses JaxMe 2 to generate JAXB source files from an XML schema
> : http://mojo.codehaus.org/xjc-maven-plugin/. I use it for my jaxb
> transformations and it's work great. Hope it's help!
>
> On 11/7/05, Wilfred Springer <[EMAIL PROTECTED] > wrote:
> >
> > All,
> >
> > Just to make sure: did anybody ever run into a Maven 2 JAXB plugin?
> > AFAIK, the only existing plugin is the one for Maven 1 and a JAXME
> > plugin at mojo.codehaus.org . I am looking for
> > a JWSDP 1.6 based version.
> >
> > Thanks,
> >
> > Wilfred
> >
> > --
> > _
> > Wilfred Springer Phone : +31 (0)3 3451 5736
> > Software Architect Mobile : +31 (0)6 2295 7321
> > Client Solutions Fax : +31 (0)3 3451 5734
> > Enterprise Web Services Mail : [EMAIL PROTECTED]
> > Sun Microsystems Netherlands AIM : wilfred springer
> > http://blogs.sun.com/wilfred/
> >
> >
> > NOTICE: This email message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged
> > information. Any unauthorized review, use, disclosure or distribution
> > is prohibited. If you are not the intended recipient, please contact
> > the sender by reply email and destroy all copies of the original
> > message.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Alexandre Poitras
> Québec, Canada




--
Alexandre Poitras
Québec, Canada

Re: [m2] JAXB Plugin

[Alexandre Poitras]

This plugin uses JaxMe 2 to generate JAXB source files from an XML schema :
http://mojo.codehaus.org/xjc-maven-plugin/. I use it for my jaxb
transformations and it's work great. Hope it's help!

On 11/7/05, Wilfred Springer <[EMAIL PROTECTED]> wrote:
>
> All,
>
> Just to make sure: did anybody ever run into a Maven 2 JAXB plugin?
> AFAIK, the only existing plugin is the one for Maven 1 and a JAXME
> plugin at mojo.codehaus.org . I am looking for a
> JWSDP 1.6 based version.
>
> Thanks,
>
> Wilfred
>
> --
> _
> Wilfred Springer Phone : +31 (0)3 3451 5736
> Software Architect Mobile : +31 (0)6 2295 7321
> Client Solutions Fax : +31 (0)3 3451 5734
> Enterprise Web Services Mail : [EMAIL PROTECTED]
> Sun Microsystems Netherlands AIM : wilfred springer
> http://blogs.sun.com/wilfred/
>
>
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact
> the sender by reply email and destroy all copies of the original
> message.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Alexandre Poitras
Québec, Canada

Tomcat APIs on repository

[João Carlos Bortoletto Junior]

Hi friends,

 

Anybody can tell me if a version 5.0.28 of tomcat APIs will be 
available at ibiblio repository soon? (At this point, I've found only 5.0.18 
version...)

Thanks!

 

João Bortoletto

 

 

Can't use maven2 (offline)

[Eric Parpal]

I tried with offline=false and file:///mypath/ibiblio/maven2 (in 
settings.xml and in the command line).

Always the same message.

Finally, are you sure you got all the dependencies of the archetype plugin 
and the archetype artifact itself?

No I am not sure because no message warns me.
The character '*' meaning that all subfiles and subdirectories have been 
downloaded, the content of my /mypath/ibiblio/maven2 directory is :

/mypath/ibiblio/maven2/org/apache/maven/archetypes/*
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-archetype-plugin/*
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-install-plugin/*
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/index.html
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml.md5
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/maven-metadata.xml.sha1
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/plugins.xml.md5
/mypath/ibiblio/maven2/plugins/org/apache/maven/plugins/plugins.xml.sha1
/mypath/ibiblio/maven2/org/apache/maven/plugins/maven-archetype-plugin/*
/mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml
/mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml.md5
/mypath/ibiblio/maven2/org/apache/maven/plugins/maven-metadata.xml.sha1

NB : I don't know the difference between org/apache/maven/plugins and 
plugins/org/apache/maven, I took both



If you are sure you have all the dependencies, and that your repository 
path is correct, you can try the fully specified invocation, which looks

like: mvn :::
I'm sure of nothing. I used url=file:///mypath/ibiblio/maven2. Is it right ? 
(I supposed that this path should stop at the directory "maven2", as the 
"internet" one does : http://www.ibiblio.org/maven2).
Do I have to define it as a "pluginRepository" or as a "repository" ? (In 
doubt, I did both)
Then, I tried mvn 
org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-3:create -D... and 
gets another message (thanks for this!) :
"Downloading 
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.pom"; 
... Error getting pom ... from the specified remote repositories: central 
(http://repo1.maven.org/maven2)"
So, I can't see mention of my repository. I don't know why. I might have 
missed something.
Besides, when I look for this file in the internet repository, I can't find 
it.

Any help or suggestion will be welcomed.
Thanks.

_
Une chance par jour de gagner un voyage au soleil avec Magic Search ! 
http://www.magicsearch.fr



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Using Maven as Eclipse class-path container

[Michael Böckling]

Hi,

I'd like to know if there is, or if there are any plans to create, an 
Eclipse plugin that cann add a Maven2 class-path container to a project, 
so there is a way to use the Maven artifact resolver (adding 
dependencies automatically to the Eclipse classpath) inside Eclipse. 
This would be especially useful for transitive depencies...

The idea for this stems from the Necessitas Ivy plugin for Eclipse:
http://kevin.oneill.id.au/2005/06/06/necessitas-jar-management-for-eclipse

Are there any informations about this topic? Maybe the soon-to-be 
released M2 Eclipse plugin 
(http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this?


Thanks,
Michael Böckling


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] install plugin bug with classifiers ?

[Julien Stern]

On Mon, Nov 07, 2005 at 01:19:11PM +, Brett Porter wrote:
> Sorry, what option are you referring to?

I'm sorry if I was not clear.
Basically, I'd like to produce a jar with debug info
and a jar without debug info (for a very size constrained environment).

So I have a profile (nodebug), where I configure the fact that debug
should be disabled.

By taking the example maven-model as you suggested, M2 produces two
jars, each of them without debug info:
- somejar-1.0.jar
- somejar-1.0-nodebug.jar

My only small issue remaining is that when I ask M2 to perform an "install",
both jars are installed and the jar with debug info (installed with
the standard profile) is replaced by the jar without debug info by the
same name.

--
Julien

> Configuration inside the execution will be restricted to that execution.
> 
> - Brett
> 
> On 11/7/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > On Mon, Nov 07, 2005 at 10:10:58AM +1100, Brett Porter wrote:
> > > Take a look at maven-model in the Maven sources. It does exactly this,
> > > and last time I checked it worked :)
> >
> > Getting closer... :)
> >
> > I was doing:
> >
> > 
> >   nodebug
> > 
> > 
> >   
> > package
> > 
> >   jar
> > 
> >   
> > 
> >
> > which failed as I described, and when I change it to:
> >
> > 
> >   
> > package
> > 
> >   jar
> > 
> > 
> >   nodebug
> > 
> >   
> > 
> >
> > the build does not fail anymore.
> >
> > However, it produces two jars:
> > - somejar-1.0.jar
> > - somejar-1.0-nodebug.jar
> >
> > but it applies the option from the profile to BOTH jars.
> > I would like it either to produce a single jar, or to produce two
> > of them, but without applying the profile rules to both jars !
> >
> > Thanks.
> >
> > --
> > Julien Stern
> >
> > >
> > > - Brett
> > >
> > > On 11/4/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > On Fri, Nov 04, 2005 at 09:22:25AM +1100, Brett Porter wrote:
> > > > > I think you need:
> > > > >
> > > > > package
> > > > >
> > > > > and
> > > > >
> > > > > 
> > > > >   jar
> > > > > 
> > > > >
> > > > > in the jar plugin as it is not being run otherwise.
> > > > >
> > > > > - Brett
> > > >
> > > > No luck with this either unfortunately.
> > > > I still have:
> > > >
> > > > [INFO] [jar:jar]
> > > > [INFO] Building jar:
> > > > /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar
> > > > [INFO] [install:install]
> > > > [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to
> > > > /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar
> > > >
> > > > I guess I'll file a bug report :)
> > > > Thanks for your help.
> > > >
> > > > --
> > > > Julien
> > > >
> > > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > > On Thu, Nov 03, 2005 at 10:05:50AM +1100, Brett Porter wrote:
> > > > > > > How are you calling it?
> > > > > > >
> > > > > > > Sounds like you are running install:install over a multiproject -
> > > > > > > instead you should use "install".
> > > > > >
> > > > > > Well, I believe I'm doing something fairly standard.
> > > > > > I'm calling:
> > > > > >
> > > > > > $ mvn -Pnodebug install
> > > > > > or
> > > > > > $ mvn -Pnodebug clean install
> > > > > >
> > > > > > With "nodebug" containing:
> > > > > >
> > > > > >   
> > > > > > 
> > > > > >   
> > > > > > true
> > > > > > org.apache.maven.plugins
> > > > > > maven-compiler-plugin
> > > > > > 
> > > > > >   true
> > > > > >   false
> > > > > >   true
> > > > > >   
> > > > > > 
> > > > > >   
> > > > > > 
> > > > > >   
> > > > > >   
> > > > > > true
> > > > > > org.apache.maven.plugins
> > > > > > maven-jar-plugin
> > > > > > 
> > > > > >   nodebug
> > > > > > 
> > > > > >   
> > > > > > 
> > > > > >   
> > > > > >
> > > > > > There are two levels of POM inheritance if that may also diagnose...
> > > > > >
> > > > > > By the way, thanks a lot for your answers to my other emails,
> > > > > > I'll try to find time to add improvements requests in JIRA.
> > > > > >
> > > > > > --
> > > > > > Julien Stern
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > I've used this successfully with classifiers before.
> > > > > > >
> > > > > > >  -Brett
> > > > > > >
> > > > > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > > > > The install plugin does not seem to work when used with 
> > > > > > > > classifiers.
> > > > > > > > When I use the jar plugin with a classifier, the install fails
> > > > > > > > (the install plugin tries to use "$MYPROJECTDIR/target/classes"
> > > > > > > > as the artifact name to install.
> > > > > > > >
> > > > > > > > Is it forbidden to use classifier with install/deploy ?
>

Re: JCOVERAGE for MAVEN 2

[stéphane bouchet]

Jcoverage is a commercial tool, prefer cobertura.

the plugin for maven2 is still in dev.

http://maven-plugins.sourceforge.net/maven-cobertura-plugin/

STéphane


REBOISSON Eric a écrit :

Is there a JCOVERAGE plugins for maven 2 ?

How to install it if it exists ?

Thanks

Eric

__

Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et 
établi à l'intention exclusive de ses destinataires. Toute utilisation de ce 
message non conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline 
toute responsabilité au titre de ce message.

This message and any attachments (the message) are confidential and intended 
solely for the addressees. Any unauthorised use or dissemination is prohibited. 
IFP should not be liable for this message.

Visitez notre site Web / Visit our web site : http://www.ifp.fr
__





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JCOVERAGE for MAVEN 2

[REBOISSON Eric]

Is there a JCOVERAGE plugins for maven 2 ?

How to install it if it exists ?

Thanks

Eric

__

Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et 
établi à l'intention exclusive de ses destinataires. Toute utilisation de ce 
message non conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline 
toute responsabilité au titre de ce message.

This message and any attachments (the message) are confidential and intended 
solely for the addressees. Any unauthorised use or dissemination is prohibited. 
IFP should not be liable for this message.

Visitez notre site Web / Visit our web site : http://www.ifp.fr
__





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] ant bug with EnumeratedAttribute task parameters=

[Anuerin Diaz]

hi again,

   im trying to debug the problem below (hoping i can find a
workaround) but since policy prevents me from installing subversion in
my workstation (even if it doesnt entail a real installer), i just
manually retrieved the maven-antrun-plugin from
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-antrun-plugin/

  i am pretty sure that i have copied the correct structure (sans the
site directory) and the latest versions of each source/resource
file[1]. i edited the pom and based it on the pom included in the
original antrun plugin jar file. my project pom looks like this

  org.apache.maven.plugins
  maven-antrun-plugin
  maven-plugin
  Maven AntRun Plugin
  1.0

  

  org.apache.maven
  maven-plugin-tools-api
  2.0


  ant
  ant
  1.6.2


  


i just inserted some printout statements to help get an idea how
things are done (my java skills need some more work). the 'impromptu'
project compiles and installs fine in my local repository but using
the plugin causes this error:


[ERROR] Nonexistent component:
org.codehaus.plexus.component.configurator.ComponentConfiguratoroverride
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-antrun-plugin:1.0:run': Unable to find
the mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.0:run' in the
plugin 'org.apache.maven.plugins:maven-antrun-plugin'

Component descriptor cannot be found in the component repository:
org.codehaus.plexus.component.configurator.ComponentConfigu
ratoroverride.
==

i noticed that the original plugin jar file has the
META-INF/plexus/component.xml and META-INF/maven/plugin.xml. My
'hijacked'  antrun plugin does no thave these files. can you point to
me what i missed? thanks.


[1] dir /s /b /a-d antrun\src
src\main\java\org\apache\maven\plugin\antrun\AbstractAntMojo.java
src\main\java\org\apache\maven\plugin\antrun\AntPropertyHelper.java
src\main\java\org\apache\maven\plugin\antrun\AntRunMojo.java
src\main\java\org\apache\maven\plugin\antrun\components\AntTargetConverter.java
src\resources\META-INF\plexus\components.xml

ciao!


On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> hi,
>
>  the attachments caused my mail to bounce so you can access the files
> using this link (combined to a single file, 8KB in total) :
>
>http://ramfree17.org/hasty/maven/antrun_issue.zip
>
>
> ciao!
>
> On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> > hi,
> >
> >  the ant-run plugin (or the launcher) seems unable to properly
> > convert attributes that are of the type EnumeratedAttribute[1]. the
> > execution always fail with an error that the attribute being set is
> > not supported by the class.
> >
> >  i have attached 3 files to serve as a test case for this.
> >
> >  1. "sample.zip" - contains the project that will serve as the main
> > test case. it really is just the plugin tutorial and i just added the
> > followign in the pom.xml so my test Task will be called during compile
> > time:
> >
> > 
> >   
> >
> >testbed
> >tests
> >1.0
> >
> >
> >ant
> >ant
> >1.5
> >
> >   
> >  
> > 
> >maven-antrun-plugin
> >
> >   
> >  compile
> > 
> >
> >>   target = "test-run"
> >   antfile = "${basedir}/build.xml">
> >
> >   
> >
> >
> > 
> > 
> >run
> >  
> >
> > 
> >  
> >   
> > 
> >
> >   2. "testbed.zip" - contains the test Ant Task jar file. the test
> > Task has one attribute that is derived from EnumeratedAttribute.
> >
> >   3.  "testbed-src.zip" - contains the source code for the testbed
> > artifact (in case somebody is interested).
> >
> >
> >   i think the problem is just with the launcher since the task runs
> > fairly well from normal Ant invocation. i found this problem when i
> > was trying to use the  task in the ant-optinoal package.
> > anybody have an idea how to work around this?
> >
> >   thanks.
> >
> > [1] http://ant.apache.org/manual/develop.html#set-magic
> >
> > ciao!
> >
> > --
> >
> > "Programming, an artform that fights back"
> >
> > Anuerin G. Diaz
> > Registered Linux User #246176
> > Friendly Linux Board @ http://mandrivausers.org/index.php
> > http://capsule.ramfree17.org , when you absolutely have nothing else
> > better to do
> >
> >
> >
>
>
> --
>
> "Programming, an artform that fights back"
>
> Anuerin G. Diaz
> Registered Linux User #246176
>

Re: Can't use maven2 (offline)

[John Casey]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

My initial guess is that since you have  set to true, it's not
accessing any remote repositories at all, regardless of whether it's got
a local mirror. Have you tried with the local mirror and offline==false?

What files did you copy over? Did you get the metadata files as well as
the jars? Finally, are you sure you got all the dependencies of the
archetype plugin and the archetype artifact itself?

One other thing I'd suggest trying is a triple-slash in your path, like
this:

file:///mypath/ibiblio/maven2

I've personally found the file: URL format to be a bit confusing, and
I'm not 100% sure what will work and what won't. The big problem here
seems to be that it cannot determine from the metadata which version of
the archetype plugin to use...by checking those maven-metadata XML files
in the repository.

If you are sure you have all the dependencies, and that your repository
path is correct, you can try the fully specified invocation, which looks
like:

mvn :::

Which should pin the plugin version down to a concrete value, and skip
any mucking around with metadata.

Let's find out what works here, and then we'll write up some formal doco
for the next guy. :)

Cheers,

John

Eric Parpal wrote:
| My working network has no connection to internet (no way).
| I download and copied the part of www.ibiblio.org/maven2 that seemed to
| me necessary to launch the first command of the Quick Start (mvn
| archetype:create), let's say under file:/mypath/ibiblio/maven2.
| I tried several things, one by one, or combined. I always failed and got
| the same message (the plugin
| org.apache.maven.plugins:maven-archetype-plugin does not exist or no
| valid version could be found).
| My big problem is that maven never says to me what's the real problem !
| Whatever the way, always the same message. No way to know if my mirror
| or my repository is ignored, or is taken into account but not correct,
| or else.
| Here are the things I tried :
|
| * a mirror defined in my settings.xml :
| 
| central
| mirror1
| file:/mypath/ibiblio/maven2
| mirror1
| 
|
| * a profile/repository defined in my settings.xml :
| 
| 
| 
| 
| repo1
| repo1
| file:/mypath/ibiblio/maven2
| 
| 
| 
| 
| repo2
| repo2
| file:/mypath/ibiblio/maven2
| 
| 
| MyProfile
| 
| 
| MyProfile
| 
| (and trying with or without -PMyProfile in the command line)
|
| * true in my settings.xml
|
| * -DremoteRepositories=file:/mypath/ibiblio/maven2 on the command line
|
|
| In fact, I think I will be obliged to use maven 1 again if nobody can
| help me :-(
|
| _
| Tout savoir sur la sécurité de vos enfants sur Internet !
| http://go.msn.fr/10-channel/80-security/protection/default.asp
|
|
| -
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDb2cJK3h2CZwO/4URAokVAKCAHTIJMhLlLlmWsi90Dbk/SR85rwCfS3MI
VApry+Q+1w5aNnIz0t0wpzE=
=d4Zl
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

location for app configuration file

[sockmonk]

Hi,

Just learning to use maven2, and I'm wondering where I should put the
properties file for configuring my app so that it will
a) be found during the junit test phase; and
b) be deployed together with the application's jar file.

I don't want to put the properties file IN the jar, because the end user
needs to be able to edit it easily. src/main/config seems like a likely
place; is there additional magic to make it visible to the app? Thanks,

--
[EMAIL PROTECTED]

Re: [M2] How to work with Eclipse Wtp and maven2

[Alexandre Poitras]

I finally found the solution. For those you are wondering the same thing,
there's the solution
http://jira.codehaus.org/browse/MNG-1430?page=all.Thank
to the submitter of the patch. Helps a lot.


On 11/3/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I found off some mails on this subject but I can't seems to get the big
> picture to how work at the same time with eclipse wtp and maven 2. The
> documentation seems very sparse and seems to use different tricks. Can
> someone who got it working give me some quick hints of the differences
> between working with Maven 2 with the regular version of eclipse and with
> eclipse Wtp.
>
> Thank for any help. Really appreciated!
>
> --
> Alexandre Poitras
> Québec, Canada




--
Alexandre Poitras
Québec, Canada

Re: [m2] ant bug with EnumeratedAttribute task parameters=

[Anuerin Diaz]

hi,

  the attachments caused my mail to bounce so you can access the files
using this link (combined to a single file, 8KB in total) :

http://ramfree17.org/hasty/maven/antrun_issue.zip


ciao!

On 11/7/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
> hi,
>
>  the ant-run plugin (or the launcher) seems unable to properly
> convert attributes that are of the type EnumeratedAttribute[1]. the
> execution always fail with an error that the attribute being set is
> not supported by the class.
>
>  i have attached 3 files to serve as a test case for this.
>
>  1. "sample.zip" - contains the project that will serve as the main
> test case. it really is just the plugin tutorial and i just added the
> followign in the pom.xml so my test Task will be called during compile
> time:
>
> 
>   
>
>testbed
>tests
>1.0
>
>
>ant
>ant
>1.5
>
>   
>  
> 
>maven-antrun-plugin
>
>   
>  compile
> 
>
>  target = "test-run"
>   antfile = "${basedir}/build.xml">
>
>   
>
>
> 
> 
>run
>  
>
> 
>  
>   
> 
>
>   2. "testbed.zip" - contains the test Ant Task jar file. the test
> Task has one attribute that is derived from EnumeratedAttribute.
>
>   3.  "testbed-src.zip" - contains the source code for the testbed
> artifact (in case somebody is interested).
>
>
>   i think the problem is just with the launcher since the task runs
> fairly well from normal Ant invocation. i found this problem when i
> was trying to use the  task in the ant-optinoal package.
> anybody have an idea how to work around this?
>
>   thanks.
>
> [1] http://ant.apache.org/manual/develop.html#set-magic
>
> ciao!
>
> --
>
> "Programming, an artform that fights back"
>
> Anuerin G. Diaz
> Registered Linux User #246176
> Friendly Linux Board @ http://mandrivausers.org/index.php
> http://capsule.ramfree17.org , when you absolutely have nothing else
> better to do
>
>
>


--

"Programming, an artform that fights back"

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Can't use maven2 (offline)

[Eric Parpal]

My working network has no connection to internet (no way).
I download and copied the part of www.ibiblio.org/maven2 that seemed to me 
necessary to launch the first command of the Quick Start (mvn 
archetype:create), let's say under file:/mypath/ibiblio/maven2.
I tried several things, one by one, or combined. I always failed and got the 
same message (the plugin org.apache.maven.plugins:maven-archetype-plugin 
does not exist or no valid version could be found).
My big problem is that maven never says to me what's the real problem ! 
Whatever the way, always the same message. No way to know if my mirror or my 
repository is ignored, or is taken into account but not correct, or else.

Here are the things I tried :

* a mirror defined in my settings.xml :

central
mirror1
file:/mypath/ibiblio/maven2
mirror1


* a profile/repository defined in my settings.xml :




repo1
repo1
file:/mypath/ibiblio/maven2




repo2
repo2
file:/mypath/ibiblio/maven2


MyProfile


MyProfile

(and trying with or without -PMyProfile in the command line)

* true in my settings.xml

* -DremoteRepositories=file:/mypath/ibiblio/maven2 on the command line


In fact, I think I will be obliged to use maven 1 again if nobody can help 
me :-(


_
Tout savoir sur la sécurité de vos enfants sur Internet ! 
http://go.msn.fr/10-channel/80-security/protection/default.asp



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

how to add source to eclipse using m2

[el wang]

when doing mvn eclipse:eclipse how to add source code
to specified jar? I remember maven 1 can do that.

any clue? thanks




__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [MAVEN 2] Update /maven.apache.org/guides/introduction/introduction-to-repositories.html

[Jeff Jensen]

Regarding the wiki/others helping, do you know that the code and docs are
available to you from subversion?  When having something to contribute, you
can get it and patch it.  I have done this many times on m1.1, and was an
easy process.  The "hardest" part was waiting for a committer to get the
patch into svn.  This usually only took up to 2 days, but did take about 2
weeks a couple of times.
 

-Original Message-
From: Jadoulle Jérôme [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 07, 2005 2:28 AM
To: users@maven.apache.org
Subject: [MAVEN 2] Update
/maven.apache.org/guides/introduction/introduction-to-repositories.html

Hello,

 

I am trying to set-up an in-house remote repository for my company.

 

We did this already in the past using maven 1.02 (though I wasn't the guy in
charge) and we now want to move to V2.0.

 

Problem is that documentation about how to do this in a generic fashion (I
don't want the connection information to be written in each POM.xml file) is
still referring to Maven 1.0 "build.properties" file... Which doesn't help
me.

So, I would be grateful to you to have this introduction to repositories to
be updated to match the V2 and it's Settings.xml file.

 

In fact, I think it would help a lot of people to have:

-  XSD schema sort of reference pages about each XML file users are
likely to change (settings.xml, pom.xml,...).

-  More precise documentation for "basic examples".  I personally
think that, in the current state, you rely too much on user's knowledge,
which is, when he starts to use maven for the first, quite limitated.

 

I am certainly not saying that you are making a bad job, not at all.  I am
just telling that I would have a far better Maven experience if more precise
documentation was made available to users.  Reference pages are very
important, I think.

 

A last note: I bet that part of your answer will tell that you prefer focus
on correcting bugs and bring more functionality to the community and that
you are already doing all what you can concerning the documentation. And
you'll be right!  But did you think about putting documentation in a wiki or
something, where all willing-to-help users would be able to make the
knowledge base grow and correct documentation errors, imperfections,... ?
Perhaps this would be a very interesting thing to do.  What do you think of
it?

 

Anyway, thank you very much for at least having read this mail,

 

Jérôme JADOULLE



**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Rijksdienst voor Pensioenen
Office National des Pensions

**



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] install plugin bug with classifiers ?

[Brett Porter]

Sorry, what option are you referring to?

Configuration inside the execution will be restricted to that execution.

- Brett

On 11/7/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 07, 2005 at 10:10:58AM +1100, Brett Porter wrote:
> > Take a look at maven-model in the Maven sources. It does exactly this,
> > and last time I checked it worked :)
>
> Getting closer... :)
>
> I was doing:
>
> 
>   nodebug
> 
> 
>   
> package
> 
>   jar
> 
>   
> 
>
> which failed as I described, and when I change it to:
>
> 
>   
> package
> 
>   jar
> 
> 
>   nodebug
> 
>   
> 
>
> the build does not fail anymore.
>
> However, it produces two jars:
> - somejar-1.0.jar
> - somejar-1.0-nodebug.jar
>
> but it applies the option from the profile to BOTH jars.
> I would like it either to produce a single jar, or to produce two
> of them, but without applying the profile rules to both jars !
>
> Thanks.
>
> --
> Julien Stern
>
> >
> > - Brett
> >
> > On 11/4/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > On Fri, Nov 04, 2005 at 09:22:25AM +1100, Brett Porter wrote:
> > > > I think you need:
> > > >
> > > > package
> > > >
> > > > and
> > > >
> > > > 
> > > >   jar
> > > > 
> > > >
> > > > in the jar plugin as it is not being run otherwise.
> > > >
> > > > - Brett
> > >
> > > No luck with this either unfortunately.
> > > I still have:
> > >
> > > [INFO] [jar:jar]
> > > [INFO] Building jar:
> > > /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar
> > > [INFO] [install:install]
> > > [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to
> > > /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar
> > >
> > > I guess I'll file a bug report :)
> > > Thanks for your help.
> > >
> > > --
> > > Julien
> > >
> > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > On Thu, Nov 03, 2005 at 10:05:50AM +1100, Brett Porter wrote:
> > > > > > How are you calling it?
> > > > > >
> > > > > > Sounds like you are running install:install over a multiproject -
> > > > > > instead you should use "install".
> > > > >
> > > > > Well, I believe I'm doing something fairly standard.
> > > > > I'm calling:
> > > > >
> > > > > $ mvn -Pnodebug install
> > > > > or
> > > > > $ mvn -Pnodebug clean install
> > > > >
> > > > > With "nodebug" containing:
> > > > >
> > > > >   
> > > > > 
> > > > >   
> > > > > true
> > > > > org.apache.maven.plugins
> > > > > maven-compiler-plugin
> > > > > 
> > > > >   true
> > > > >   false
> > > > >   true
> > > > >   
> > > > > 
> > > > >   
> > > > > 
> > > > >   
> > > > >   
> > > > > true
> > > > > org.apache.maven.plugins
> > > > > maven-jar-plugin
> > > > > 
> > > > >   nodebug
> > > > > 
> > > > >   
> > > > > 
> > > > >   
> > > > >
> > > > > There are two levels of POM inheritance if that may also diagnose...
> > > > >
> > > > > By the way, thanks a lot for your answers to my other emails,
> > > > > I'll try to find time to add improvements requests in JIRA.
> > > > >
> > > > > --
> > > > > Julien Stern
> > > > >
> > > > >
> > > > > >
> > > > > > I've used this successfully with classifiers before.
> > > > > >
> > > > > >  -Brett
> > > > > >
> > > > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > > > The install plugin does not seem to work when used with 
> > > > > > > classifiers.
> > > > > > > When I use the jar plugin with a classifier, the install fails
> > > > > > > (the install plugin tries to use "$MYPROJECTDIR/target/classes"
> > > > > > > as the artifact name to install.
> > > > > > >
> > > > > > > Is it forbidden to use classifier with install/deploy ?
> > > > > > > Or is it a bug ?
> > > > > > > Or is there a correct way to configure the use of this case ?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > --
> > > > > > > Julien Stern
> > > > > > >
> > > > > > >
> > > > > > > -
> > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > -
> > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > >
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > > -
> > > > To uns

optional project dependencies for eclipse workspace

[Bernd Mau]

Hi,

assuming the following scenario:

Module B depends on module A. You are using elcipse and you have to
implement a new function for module B. Both modules belong to a huge
project and until now you're quite happy that you only needed to check
module B. 

During your work you find out that you have to make some changes in
module A as well. Fine, you can check out module A, make the changes to
fullfill the requirements of module B and finally you will call 'mvn
install' to make the changes available for module B. 

Likely you have to repeat the last two steps several times and you may
wish to have project dependencies rather than binary dependencies.
Still, you don't want to check out and import the huge project.

At this point I would like to tell the eclipse plugin to search for
dependencies of module B in my eclipse workspace. If there are any
matching modules, here module A, please refer to the eclipse project of
module A.

This may look like this:
mvn eclipse:eclipse -Declipse.workspace=true

Bernd


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mvn eclipse:eclipse try to download dependency jar doesn't exist

[el wang]

it finally works. i have to install jdk's tools.jar to
m2 repository. :-(

--- el wang <[EMAIL PROTECTED]> wrote:

> thanks stephen, jsf is my fault. but m2 still ask me
> to download
>
http://repo1.maven.org/maven2/java/tools/1.4/tools-1.4.jar
> 
> what is this?
> 
> 
> --- Stephen Coy <[EMAIL PROTECTED]> wrote:
> 
> >
>

> > 
> > 
> > On 07/11/2005, at 10:55 PM, el wang wrote:
> > 
> > > in my pom.xml, add
> > springframework:spring-mmock:1.2.3
> > > to it's dependency. when try to test my code.
> > using
> > > #mvn eclispe:eclipse also got the same result.
> > >
> > > m2 told me that it can't find  jsf-api-1.1.jar
> or
> > jdbc-stdext-2.0.jar
> > >
> > >
> > >   
> > > __
> > > Start your day with Yahoo! - Make it your home
> > page!
> > > http://www.yahoo.com/r/hs
> > >
> > >
> >
>
-
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > >
> > 
> > 
> >
>
-
> > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > 
> > 
> 
> 
> 
>   
> __ 
> Yahoo! FareChase: Search multiple travel sites in
> one click.
> http://farechase.yahoo.com
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 




__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mvn eclipse:eclipse try to download dependency jar doesn't exist

[el wang]

thanks stephen, jsf is my fault. but m2 still ask me
to download
http://repo1.maven.org/maven2/java/tools/1.4/tools-1.4.jar

what is this?


--- Stephen Coy <[EMAIL PROTECTED]> wrote:

>

> 
> 
> On 07/11/2005, at 10:55 PM, el wang wrote:
> 
> > in my pom.xml, add
> springframework:spring-mmock:1.2.3
> > to it's dependency. when try to test my code.
> using
> > #mvn eclispe:eclipse also got the same result.
> >
> > m2 told me that it can't find  jsf-api-1.1.jar or
> jdbc-stdext-2.0.jar
> >
> >
> > 
> > __
> > Start your day with Yahoo! - Make it your home
> page!
> > http://www.yahoo.com/r/hs
> >
> >
>
-
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 




__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [M2] javadoc definining group packagings

[Pilgrim, Peter]

I am sorry I asked this question already, but ...

How do set up the group packaging with the javadoc plug-in?

>From the documentation
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html

"Separates packages on the overview page into whatever groups you 
specify, one group per table. See group. It is a comma separated String."


Which refers to the JavaDoc official documentation for -group parameter


"-group  groupheading  packagepattern:packagepattern:...

"Separates packages on the overview page into whatever groups you
specify, one group per table. You specify each group with a 
different -group option. The groups appear on the page in the
order specified on the command line; packages are alphabetized 
within a group. For a given -group option, the packages matching 
the list of packagepattern expressions appear in a table with 
the heading groupheading."

e.g. C:> javadoc -group "Core Packages" "java.lang*:java.util"
-group "Extension Packages" "javax.*"
java.lang java.lang.reflect java.util javax.servlet java.new


Is the javadoc plug-in simply passing these strings to the Java doclet
generator, or those it expecting a specific format in order to
translate to the proper javadoc -group format? 

The m2 debug does not really reveal what the fault is.





Any help appreciated.


> -Original Message-
> From: Pilgrim, Peter [mailto:[EMAIL PROTECTED]
> Sent: 03 November 2005 13:29
> To: Maven Users List (E-mail)
> Subject: [M2] javadoc definining group packagings
> 
> 
> Hi 
> 
> I am converting M1 to M2 and I trying set up the javadoc 
> groups for packages.
> 
> What is the correct format for  in the javadoc:javadoc plugin?
> 
> I would like `com.csfb.foo.bar.dao' to fall under DAO
> and `com.csfb.foo.bar.ui' to fall under `UI'
> 
> 
>   
>   ...
>  
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 
> true
> 
> 
> 
> Copyright me
> true
> 
> http://java.sun.com/j2se/1.4.2/docs/api,
> http://maven.apache.org/apidocs/
> 
> 
> "Data Access Objects"
> "com.csfb.foo.bar.dao"
> "com.csfb.foo.bar.dao.config"
> "com.csfb.foo.bar.da.impl"
> 
> "User Interface"
> "com.csfb.foo.bar.ui"
> "com.csfb.foo.bar.ui.services"
>   
>   ...
>
>
> 
>   ...
> 
> 
> 
> tia
====

--
Peter Pilgrim :: J2EE Software Development
Operations/IT - Credit Suisse First Boston, 
Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom
Tel: +44-(0)207-883-4497


==
Please access the attached hyperlink for an important electronic communications 
disclaimer: 

http://www.csfb.com/legal_terms/disclaimer_external_email.shtml

==


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] ear packaging

[Stephane Nicoll]

Chris,

The info is located in http://jira.codehaus.org/browse/MNG-699 (see a patch
on components.xml which adds the par and ejb3 lifecycle.

Cheers,
Stéphane

On 11/4/05, Chris Tucker <[EMAIL PROTECTED]> wrote:
>
> > You can find J2EE project skeleton at: http://www.bzdyl.net/demo-app.zip
> > (I have created for J2EE ver. 5 but it is easy to customize it to your
> > needs. It uses maven-par-plugin and maven-ejb3-plugin which are
> > currently in maven sandbox in the repository. I don't know if you can
> > find them deployed in any maven repository, it is possible that you will
> > need to checkout maven 2 sources and build them locally).
>
> Are you using the maven-par-plugin straight from svn? From what I can
> tell it doesn't define a  type for .par, so I've been having
> to manually invoke par:par; it looks from your demo app that you already
> have a suitable packaging working. Would you be willing to share your
> diffs against the svn versions of the par and ejb3 plugins?
>
> Cheers,
> Chris
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
.::You're welcome ::.

Re: [m2] config of goals

[David Sag]

Further to this, I have posted an issue in JIRA

http://jira.codehaus.org/browse/MNG-1446

Unable to config goals that are not bound to part of the standard 
lifecycle

cheers

dave


David Sag <[EMAIL PROTECTED]> wrote on 07-11-2005 08:50:51:

> 
> I am having real problems getting my plugin config to work. 
> 
> Here's my use case: 
> 
> a developer compiles and as part of her build checkstyle must be run
> and fail a build on any checkstyle errors. 
> this is easy and works fine. 
> 
> but within the same pom.xml file 
> 
> Continuum needs to build everything and, whether the build fails or 
> not, needs to then run the qalab plugin's merge goal with specific 
> config telling it to use the results generated by checkstyle. 
> 
> the QALab plugin has three different goals and only a few of their 
> config params are in common with each other.  so each goal must have
> its own config. 
> 
> So right now, for simplicity's sake, I just want the qalab:merge goal to 
work.
> 
> my build section is as follows: 
> 
>  
>  
>  
> org.apache.maven.plugins 
> maven-compiler-plugin 
>  
> 1.4 
> 1.4 
>  
>  
>  
> org.apache.maven.plugins 
> maven-javadoc-plugin 
>  
> 1.4 
>  
>  
>  
> org.apache.maven.plugins 
> maven-checkstyle-plugin 
>  
> xml 
> true 
>  
>  
>  
> check-main-src 
> compile 
>  
> ${project.build.directory}
> /checkstyle-result.xml 
>  
>  
>checkstyle 
>  
>  
>   
>  
>  
> net.objectlab 
> maven-qalab-plugin 
>  
>  
>  
> net.objectlab.qalab.parser.
> CheckstyleStatMerge 
> ${project.build.directory}
> /checkstyle-result.xml 
>  
>  
>merge 
>  
>  
>   
>  
>  
>  
> 
> the checkstyle plugin works fine but when I try 
> 
> %mvn qalab:merge 
> 
> i get 
> 
> [ERROR] BUILD ERROR 
> [INFO] 
> 
 

> [INFO] One or more required plugin parameters are invalid/missing 
> for 'qalab:merge' 
> 
> [0] inside the definition for plugin: 'maven-qalab-plugin'specify 
> the following: 
> 
>  
>   ... 
>   VALUE 
> . 
> 
> [1] inside the definition for plugin: 'maven-qalab-plugin'specify 
> the following: 
> 
>  
>   ... 
>   VALUE 
> . 
> 
> if i move the config from the executions block such that it is like so: 
> 
>  
> net.objectlab 
> maven-qalab-plugin 
>  
> net.objectlab.qalab.parser.CheckstyleStatMerge 
> ${project.build.directory}/checkstyle-result.
> xml 
>  
>  
> 
> then the params are accepted, but now I can't have different params 
> for the different goals, indeed i can't see how i'd go about 
> specifying different configs for the different goals in such a case.
> I need goal specific parameter config, not plugin-wide config.  or 
> should I make these goals into totally different plugins instead? 
> 
> cheers 
> 
> dave
> 
> Kind regards,
> Dave Sag 
> 
> 
> [image removed] 
> 
> 

Re: mvn eclipse:eclipse try to download dependency jar doesn't exist

[Stephen Coy]

On 07/11/2005, at 10:55 PM, el wang wrote:


in my pom.xml, add springframework:spring-mmock:1.2.3
to it's dependency. when try to test my code. using
#mvn eclispe:eclipse also got the same result.

m2 told me that it can't find  jsf-api-1.1.jar or jdbc-stdext-2.0.jar



__
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] release:perform does not work

[Bernd Mau]

Hi Jose,

for editing master and intermediate POMs in Eclipse I  check out the
relevant project and all its children. On the one hand this approach
makes sense as changes influences all child projects. On the other hand
editing parent POMs shouldn't be a daily business.

Best regards
Bernd

>>> [EMAIL PROTECTED] 04.11.05 12.55 >>>
2005/11/4, Bernd Mau <[EMAIL PROTECTED]>:
> Hi,
>
>
> * Independently, I can't see many advantages for using a flat layout
> instead of hierachical project structure. The subject has been taken
up
> in the Eclipse Mini Guide:
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html
>

What about editing the master and all intermediate POMs in Eclipse?
What's the recommended approach for this if using a hierarchical
project structure and Eclipse?

Best regards
Jose

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mvn eclipse:eclipse try to download dependency jar doesn't exist

[el wang]

in my pom.xml, add springframework:spring-mmock:1.2.3
to it's dependency. when try to test my code. using 
#mvn eclispe:eclipse also got the same result.

m2 told me that it can't find  jsf-api-1.1.jar or jdbc-stdext-2.0.jar



__ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m2] JAXB Plugin

[Wilfred Springer]

All,

Just to make sure: did anybody ever run into a Maven 2 JAXB plugin?
AFAIK, the only existing plugin is the one for Maven 1 and a JAXME
plugin at mojo.codehaus.org. I am looking for a JWSDP 1.6 based version.

Thanks,

Wilfred

-- 
_
Wilfred SpringerPhone  : +31 (0)3 3451 5736
Software Architect  Mobile : +31 (0)6 2295 7321
Client SolutionsFax: +31 (0)3 3451 5734
Enterprise Web Services Mail   : [EMAIL PROTECTED]
Sun Microsystems NetherlandsAIM: wilfred springer
http://blogs.sun.com/wilfred/


NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

site configuration

[Anjan Kumar Pradhan]

Hello All,
I am using M2. I want to use site configuration (like site.xml, download
page etc.) of a different project in my current project. But I don't want to
use the relative paths. How can I specify this in my current project?
 Thanks in Advance
 Anjan

RE: [m2] Strange Build Error

[Allison, Bob]

Done.  http://jira.codehaus.org/browse/MNG-1445

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 06, 2005 18:19
To: Maven Users List
Subject: Re: [m2] Strange Build Error


Do you want to file a bug for the error reporting?

Thanks,
Brett

On 11/5/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> I figured out what caused this:  A jar file listed as a plugin in your
> POM that does not contain META-INF/maven/plugin.xml
>
> -Original Message-
> From: Allison, Bob [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 03, 2005 11:09
> To: Maven Users List
> Subject: [m2] Strange Build Error
>
>
> I am experimenting with a directory archiver for plexus, and built a
new
> snapshot version of the component.  When I did a "mvn install" in that
> directory, the install placed the jar where I expected it:
>
> [INFO] [install:install]
> [INFO] Installing
>
/net/home/allisord/src/plugins/plexus-archiver/target/plexus-archiver-1.
> 0-alpha-4-SNAPSHOT.jar to
>
/home/allisord/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-al
> pha-4-SNAPSHOT/plexus-archiver-1.0-alpha-4-SNAPSHOT.jar
>
>
> The strange part is when I went to compile against the component.  I
> changed the project to declare a dependency to
> org.codehaus.plexus:plexus-archiver:1.0-alpha-4-SNAPSHOT (instead of
> 1.0-alpha-3) and got the following:
>
> [EMAIL PROTECTED] rpm]$ mvn -X compile
> + Error stacktraces are turned on.
> [DEBUG] Building Maven user-level plugin registry from:
> '/home/allisord/.m2/plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from:
> '/opt/maven/2/conf/plugin-registry.xml'
> [INFO] Scanning for projects...
> [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml'
for
> project: qaccess.plugins:maven-rpm-plugin:maven-plugin:1.0.0
> [INFO]
>

> 
> [INFO] Building RPM Plugin for Maven
> [INFO]task-segment: [compile]
> [INFO]
>

> 
> [DEBUG] maven-plugin-plugin: resolved to version 2.0 from repository
> central
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-plugin-plugin:maven-plugin:2.0
> [DEBUG] maven-resources-plugin: resolved to version 2.1 from
repository
> central
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-resources-plugin:maven-plugin:2.1
> [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository
> central
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-compiler-plugin:maven-plugin:2.0
> [DEBUG] Skipping disabled repository central
> [DEBUG] Skipping disabled repository central
> [DEBUG] plexus-archiver: using locally installed snapshot
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:plexus-archiver:jar:1.0-alpha-4-SNAPSHOT
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.codehaus.plexus:plexus-components:pom:1.1.4
> [DEBUG] plexus-archiver: using locally installed snapshot
> [INFO]
>

> 
> [ERROR] FATAL ERROR
> [INFO]
>

> 
> [INFO] null
> [INFO]
>

> 
> [DEBUG] Trace
> java.lang.NullPointerException
> at
>
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana
> ger.java:292)
> at
>
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau
> ltPluginManager.java:198)
> at
>
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
> anager.java:163)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
> LifecycleExecutor.java:1095)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl
> e(DefaultLifecycleExecutor.java:1060)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
> ppings(DefaultLifecycleExecutor.java:869)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
> ifecycleExecutor.java:447)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures(DefaultLifecycleExecutor.java:301)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:268)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:137)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
> at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAcce

Re: [m2] aspectj

[stéphane bouchet]

Hi,

In my case, i will not upgrade to maven2 unless an aspectj plugin.
I am like the majority of users, because my project uses java 1.4 and i cannot 
change that prereq.


So for the moment I will wait for a plugin before migrate to maven2.

And if there wil not be a plugin, i will try to write one ;)


Regards,


Stéphane

Kaare Nilsen a écrit :

You should not rely on the number of people that asks for priority.
The persons that asks are the one who already have a motivation of
using maven, the wast majority i would suspect checks if maven have a
plugin for it, if not they would use something else.

I for sure would not use maven if i was not on a java 1.5 project due
to the fact of the missing aspectJ plugin. But luckily using aspectJ 5
and java 1.5 i don't need a special compiler.

With all that said. Maven2 really has made my building way more easy,
and if you could use java 1.5 and aspectJ 5 that is a working
combination

/Kaare Nilsen

On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:


I don't believe this is currently working.

You're probably the 3rd person that has asked all year - so that
probably justifies the priority :) That's possibly just a matter of it
not being there though - I'm sure if it was started more would come
out of the woodwork.

There has been some discussion on this list in the past about possible
ways to implement it - if you are interested in searching for that,
revieweing, and reviving the discussion, we'd really appreciate
anything you are able to contribute.

For myself, I'm not an aspectj user.

Cheers,
Brett

On 11/5/05, Eduardo Rocha <[EMAIL PROTECTED]> wrote:


I have seen in Maven Plugin Matrix that AspectJ Plugin for Maven 2 is
considered "Low Priority" (!) and it is yet to be done. However, I was
googling around and found some Maven2 compilers besides javac
(eclipse, aspectj), called plexus-SOMENAME-compiler. I saw in this
mail list as well someone trying to use csharp compiler as well.

Does anyone already has AspectJ + Maven 2 working?
Does anyone know how to properly use these plexus compilers?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How-to for building for different environments

[Mark Hobson]

Hi Janek,

I also use a similar configuration, but I move all the profile-related
files into src/main/profiles, e.g.:

src
|_ main
  |_ filters
|_ filter.properties
  |_ java
|_ *.java
  |_ profiles
|_ default
  |_ filters
|_ filter.properties
  |_ resources
|_ ...
|_ demo
  |_ ...
|_ live
  |_ ...
  |_ resources
|_ webapp
  |_ ...
|_ webapp-filtered
  |_ ...

You can also simplify your pom by using properties, for example here's
mine that uses the above structure:


...

${profile.finalName}


src/main/resources



src/main/profiles/${profile.name}/resources


src/main/webapp-filtered
../${profile.finalName}
true



src/main/filters/filter.properties

src/main/profiles/${profile.name}/filters/filter.properties





default

true


default
app



demo

demo
ROOT



live

live
ROOT



...


Would be good to decide on a standard and document it on the site.

Cheers,

Mark

On 06/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Thanks for this Janek.
>
> I'd encourage people to give thier feedback on this, and if possible
> if someone such as Janek could contribute this as an apt document for
> the website under the guides section, it would be much appreciated.
>
> If you'd like to use wiki.apache.org/maven to collaborate on this, you
> are welcome to.
>
> Regards,
> Brett
>
> On 11/5/05, Claus, Janek (NIH/NICHD) <[EMAIL PROTECTED]> wrote:
> >
> > All,
> >
> > I wanted to give something back to the community. For all of you, who would 
> > like to know
> > how to structure a web application in a way that it can be build for 
> > different
> > environments, here is the solution:
> >
> > I combined several previous posts and my ideas, this application uses 
> > different resources
> > for different environments (profiles) as well as diffenent filters.
> >
> > I filter the context.xml for Tomcat and web.xml, but use totally different 
> > log4j.xml's for
> > the different environments.
> > In addition I have resources that go unfiltered to all environments 
> > (Hibernate
> > configuration files).
> >
> > Create a directory layout similar to this:
> >
> > app
> > |
> > +- src
> >  |
> >  +- main
> >  |
> >  +- filter
> >  |   |
> >  |   +- dev (filter properties for your local development)
> >  |   |
> >  |   +- prod (filter props for production)
> >  |
> >  +- java
> >  |
> >  +- resources
> >  |   |
> >  |   +- all (resources for all environments)
> >  |   |
> >  |   +- dev
> >  |   |
> >  |   +- prod
> >  |
> >  +- webapp
> >  |
> >  +- webapp-filtered
> >  |
> >  +- META-INF (e.g. context.xml)
> >  |
> >  +- WEB-INF (e.g. web.xml)
> >
> > Your pom should look something like this then:
> >
> > ...
> >
> >
> >  app
> >  
> > 
> > 
> >   src/main/resources/all
> > 
> >  
> > 
> >
> >
> >  
> >  
> >dev
> >
> >  true
> >
> >
> >  
> >
> >  src/main/resources/dev
> >
> >
> >  src/main/webapp-filtered
> >  ../app 
> >  true
> >
> >  
> >  
> >src/main/filter/dev/context.properties
> >src/main/filter/dev/web.properties
> >  
> >
> >  
> >
> >  
> >  
> >prod
> >
> >  
> >
> >  src/main/resources/prod
> >
> >
> >  src/main/webapp-filtered
> >  ../app 
> >  true
> >
> >  
> >  
> >src/main/filter/prod/context.properties
> >src/main/filter/prod/web.prop

Re: Source Archives?

[Milos Kleint]

not all projects are released through maven. some are just uploaded to repo.
is there a policy to include the javadoc and sources with these as well?

Milos

On 11/6/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> This is possible with Maven 2.x (the Maven libraries certainly do it
> already) - what will be important is ensuring that projects themselves
> utilise this functionality.
>
> - Brett
>
> On 11/7/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > recently I came into a situation where I suspected a bug in
> > servlet-api-2.4.jar. No problem, it seems: This is open source software,
> > get the sources, add them to you Eclipse project and start debugging.
> >
> > It turned out not so easy: For starters, what are the exact sources of
> > servlet-api-2.4.jar? Do I need to get a particular version of Tomcat? Do
> > I need to checkout a certain svn or cvs tag? I've been losing about 3
> > hours to get the debugger up and running. (Of course, it turned out,
> > that the bug was on my side, having read the specification wrong.)
> >
> > My personal conclusion is this: It is a bad thing, that we do not
> > distribute the sources together with the jar files. Of course, there are
> > cases where the license forbids. But at least for ASL licensed jar
> > files, it ought to be absolutely no problem to add the sources to
> ibiblio.
> >
> > Additionally, one might request downloads for the source files in order
> > to make eclipse:eclipse mount them automatically.
> >
> >
> > What do you think?
> >
> >
> > Jochen
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: Multiple source directories (again)

[Daniel Or]

I have written a simple plugin that enables addition of source dirs.
If you're interested I can send it to you.

__
 
Daniel Or
_._._._._._._._._.
-Original Message-
From: Aleksandar Likic [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 06, 2005 7:50 PM
To: users@maven.apache.org
Subject: Multiple source directories (again)

I am trying to find out how to tell maven 2 to compile multiple source
directories. I am using JAXB to generate code in target/src, and then
compile it together with the rest of the code. I could have multiple
projects, but it simply doesn't make sense to me to in this particular
case.
The build process would become more complex to manage, with an extra
artifact that I don't want to have. Any ideas?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Source Archives?

[Jochen Wiedmann]

Brett Porter wrote:


> This triggers the extra attachments defined here:
> http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?rev=326633&view=markup

Thanks for the hint, Brett. I'll give it a try.


Jochen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] install plugin bug with classifiers ?

[Julien Stern]

On Mon, Nov 07, 2005 at 10:10:58AM +1100, Brett Porter wrote:
> Take a look at maven-model in the Maven sources. It does exactly this,
> and last time I checked it worked :)

Getting closer... :)

I was doing:


  nodebug


  
package

  jar

  


which failed as I described, and when I change it to:


  
package

  jar


  nodebug

  


the build does not fail anymore.

However, it produces two jars:
- somejar-1.0.jar
- somejar-1.0-nodebug.jar

but it applies the option from the profile to BOTH jars.
I would like it either to produce a single jar, or to produce two
of them, but without applying the profile rules to both jars !

Thanks.

--
Julien Stern

> 
> - Brett
> 
> On 11/4/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > On Fri, Nov 04, 2005 at 09:22:25AM +1100, Brett Porter wrote:
> > > I think you need:
> > >
> > > package
> > >
> > > and
> > >
> > > 
> > >   jar
> > > 
> > >
> > > in the jar plugin as it is not being run otherwise.
> > >
> > > - Brett
> >
> > No luck with this either unfortunately.
> > I still have:
> >
> > [INFO] [jar:jar]
> > [INFO] Building jar:
> > /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar
> > [INFO] [install:install]
> > [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to
> > /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar
> >
> > I guess I'll file a bug report :)
> > Thanks for your help.
> >
> > --
> > Julien
> >
> > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > On Thu, Nov 03, 2005 at 10:05:50AM +1100, Brett Porter wrote:
> > > > > How are you calling it?
> > > > >
> > > > > Sounds like you are running install:install over a multiproject -
> > > > > instead you should use "install".
> > > >
> > > > Well, I believe I'm doing something fairly standard.
> > > > I'm calling:
> > > >
> > > > $ mvn -Pnodebug install
> > > > or
> > > > $ mvn -Pnodebug clean install
> > > >
> > > > With "nodebug" containing:
> > > >
> > > >   
> > > > 
> > > >   
> > > > true
> > > > org.apache.maven.plugins
> > > > maven-compiler-plugin
> > > > 
> > > >   true
> > > >   false
> > > >   true
> > > >   
> > > > 
> > > >   
> > > > 
> > > >   
> > > >   
> > > > true
> > > > org.apache.maven.plugins
> > > > maven-jar-plugin
> > > > 
> > > >   nodebug
> > > > 
> > > >   
> > > > 
> > > >   
> > > >
> > > > There are two levels of POM inheritance if that may also diagnose...
> > > >
> > > > By the way, thanks a lot for your answers to my other emails,
> > > > I'll try to find time to add improvements requests in JIRA.
> > > >
> > > > --
> > > > Julien Stern
> > > >
> > > >
> > > > >
> > > > > I've used this successfully with classifiers before.
> > > > >
> > > > >  -Brett
> > > > >
> > > > > On 11/3/05, Julien Stern <[EMAIL PROTECTED]> wrote:
> > > > > > The install plugin does not seem to work when used with classifiers.
> > > > > > When I use the jar plugin with a classifier, the install fails
> > > > > > (the install plugin tries to use "$MYPROJECTDIR/target/classes"
> > > > > > as the artifact name to install.
> > > > > >
> > > > > > Is it forbidden to use classifier with install/deploy ?
> > > > > > Or is it a bug ?
> > > > > > Or is there a correct way to configure the use of this case ?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --
> > > > > > Julien Stern
> > > > > >
> > > > > >
> > > > > > -
> > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---

maven properties?

[Anuerin Diaz]

hi,

  i have been trying to reference the target build properties to no
avail. i have already searched the archives and hit this thread[1] to
no avail. i did not specify any output directories in my pom so am I
encountering the same problem in this part[2] of the thread? i have
already read the introduction to the pom and have tried "echo-ing" the
following properties:

  
maven-antrun-plugin


compile



${build.target.dir}
${build.dir}
${build.local.dir}
${build.directory}
${build.outputDirectory}
${directory}
${outputDirectory}
${project.directory}
${project.outputDirectory}
${project.build.directory}
${project.build.outputDirectory}

${pom.build.directory}
${pom.build.outputDirectory}

${artifactId}
${repository.id}







but  i am not getting anything. the last two was just sanity checks
that the properties could be referenced as specified in the thread and
not just property references. here is my output

[INFO] Executing tasks
 [echo] ${build.target.dir}
 [echo] ${build.dir}
 [echo] ${build.local.dir}
 [echo] ${build.directory}
 [echo] ${build.outputDirectory}
 [echo] ${directory}
 [echo] ${outputDirectory}
 [echo] ${project.directory}
 [echo] ${project.outputDirectory}
 [echo] ${project.build.directory}
 [echo] ${project.build.outputDirectory}
 [echo]
 [echo] ${pom.build.directory}
 [echo] ${pom.build.outputDirectory}
 [echo]
 [echo] MOD1
 [echo] my.app:MOD1:jar:1.0

maybe a table of such properties would be a great addition on the wiki
site[3]? or will there be a separate wiki site for maven2?

thanks and have a nice day.

  [1] http://www.mail-archive.com/users@maven.apache.org/msg26517.html
  [2] http://www.mail-archive.com/users@maven.apache.org/msg26521.html
  [3] http://wiki.apache.org/maven/

ciao!

--

"Programming, an artform that fights back"

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[MAVEN 2] Update /maven.apache.org/guides/introduction/introduction-to-repositories.html

[Jadoulle Jérôme]

Hello,

 

I am trying to set-up an in-house remote repository for my company.

 

We did this already in the past using maven 1.02 (though I wasn't the guy in 
charge) and we now want to move to V2.0.

 

Problem is that documentation about how to do this in a generic fashion (I 
don't want the connection information to be written in each POM.xml file) is 
still referring to Maven 1.0 "build.properties" file... Which doesn't help me.

So, I would be grateful to you to have this introduction to repositories to be 
updated to match the V2 and it's Settings.xml file.

 

In fact, I think it would help a lot of people to have:

-  XSD schema sort of reference pages about each XML file users are 
likely to change (settings.xml, pom.xml,...).

-  More precise documentation for "basic examples".  I personally think 
that, in the current state, you rely too much on user's knowledge, which is, 
when he starts to use maven for the first, quite limitated.

 

I am certainly not saying that you are making a bad job, not at all.  I am just 
telling that I would have a far better Maven experience if more precise 
documentation was made available to users.  Reference pages are very important, 
I think.

 

A last note: I bet that part of your answer will tell that you prefer focus on 
correcting bugs and bring more functionality to the community and that you are 
already doing all what you can concerning the documentation. And you'll be 
right!  But did you think about putting documentation in a wiki or something, 
where all willing-to-help users would be able to make the knowledge base grow 
and correct documentation errors, imperfections,... ?  Perhaps this would be a 
very interesting thing to do.  What do you think of it?

 

Anyway, thank you very much for at least having read this mail,

 

Jérôme JADOULLE



**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
Rijksdienst voor Pensioenen
Office National des Pensions

**

Re: [m2] aspectj

[Kaare Nilsen]

You should not rely on the number of people that asks for priority.
The persons that asks are the one who already have a motivation of
using maven, the wast majority i would suspect checks if maven have a
plugin for it, if not they would use something else.

I for sure would not use maven if i was not on a java 1.5 project due
to the fact of the missing aspectJ plugin. But luckily using aspectJ 5
and java 1.5 i don't need a special compiler.

With all that said. Maven2 really has made my building way more easy,
and if you could use java 1.5 and aspectJ 5 that is a working
combination

/Kaare Nilsen

On 07/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> I don't believe this is currently working.
>
> You're probably the 3rd person that has asked all year - so that
> probably justifies the priority :) That's possibly just a matter of it
> not being there though - I'm sure if it was started more would come
> out of the woodwork.
>
> There has been some discussion on this list in the past about possible
> ways to implement it - if you are interested in searching for that,
> revieweing, and reviving the discussion, we'd really appreciate
> anything you are able to contribute.
>
> For myself, I'm not an aspectj user.
>
> Cheers,
> Brett
>
> On 11/5/05, Eduardo Rocha <[EMAIL PROTECTED]> wrote:
> > I have seen in Maven Plugin Matrix that AspectJ Plugin for Maven 2 is
> > considered "Low Priority" (!) and it is yet to be done. However, I was
> > googling around and found some Maven2 compilers besides javac
> > (eclipse, aspectj), called plexus-SOMENAME-compiler. I saw in this
> > mail list as well someone trying to use csharp compiler as well.
> >
> > Does anyone already has AspectJ + Maven 2 working?
> > Does anyone know how to properly use these plexus compilers?
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]