Re: jar:deploy error

[Brett Porter]

Please install Artifact 1.6 - the 1.5.2 release was not compatible with 
1.1-beta-1 (even though it was bundled with it).

I have added a cautionary note to the website.

- Brett

On 9/3/05, Fernando Ney <[EMAIL PROTECTED]> wrote:
> 
> Hi,
> When using jar:deploy to deploy a jar from windows to linux machine, i get
> the following error:
> 
> BUILD FAILED
> File.. C:\Documents and 
> Settings\Fernando.Nascimento\.maven\cache\maven-
> artifact-plugin-1.5.2\plugin.jelly
> Element... artifact:artifact-deploy
> Line.. 90
> Column 9
> org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V
> 
> My properties look like this:
> maven.repo.list=repo
> maven.repo.repo=scp://10.2.1.7/
> maven.repo.ouvidor.username=xxx
> maven.repo.ouvidor.password=xxx
> maven.repo.ouvidor.directory=/home/ouvidor/repository
> maven.repo.ouvidor.scp.executable=S:\Programs\pscp.exe
> maven.remote.group=team
> maven.repo.remote=http://www.ibiblio.org/maven/,http://10.2.1.7/repository
> 
> --
> Fernando Ney
> 
>

Re: [M2] Problems with m2 site:site

[Brett Porter]

MNG-476 is already fixed.

On 9/2/05, Yann Le Du <[EMAIL PROTECTED]> wrote:
> 
> Indeed, http://jira.codehaus.org/browse/MNG-476, then
> http://jira.codehaus.org/browse/WAGONSSH-5
> 
> Though, there seems to be no fix planned for next release.
>

Re: How to set a plugin's prefix?

[dan tran]

I am not well versed in settings.xml yet.. but if you really post you 
settings.xml, it would help ;-)
 -D

 On 9/2/05, Wendell Beckwith <[EMAIL PROTECTED]> wrote: 
> 
> I really hate to be dense, but I have created a settings.cml file with the
> following content and placed it in my .m2 directory, and the project 
> itsself
> to no avail. I simply can't execute my plugin by the prefix. I looked at
> test it0031 and this provides no clues (for me at least) on how to 
> configure
> this. Is there a better explanation or roadmap on how to achieve this
> behavior? If I need to actually debug maven to discover what is or isn't
> going on where do I start? What code should I be setting break points in?
> 
> Wb
> 
>

Re: How to change the copyright info for a site build?

[dan tran]

I have not tried m2 site yet, but in m1, it is from your project.xml 's 
organization. Should not be diffrent
for m2.
 -D

 On 9/2/05, Wendell Beckwith <[EMAIL PROTECTED]> wrote: 
> 
> When using the site:site goal how do I configure the copyright message
> that's added to all the pages (we're using APT)? This is important since
> management and legal get the willies just using open source let alone 
> having
> that open source what is built as copyrighted by the Apache Software
> Foundation.
> 
> Wb
> 
>

jar:deploy error

[Fernando Ney]

Hi,
When using jar:deploy to deploy a jar from windows to linux machine, i get 
the following error:

BUILD FAILED
File.. C:\Documents and Settings\Fernando.Nascimento\.maven\cache\maven-
artifact-plugin-1.5.2\plugin.jelly
Element... artifact:artifact-deploy
Line.. 90
Column 9
org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V

My properties look like this:
maven.repo.list=repo
maven.repo.repo=scp://10.2.1.7/
maven.repo.ouvidor.username=xxx
maven.repo.ouvidor.password=xxx
maven.repo.ouvidor.directory=/home/ouvidor/repository
maven.repo.ouvidor.scp.executable=S:\Programs\pscp.exe
maven.remote.group=team
maven.repo.remote=http://www.ibiblio.org/maven/,http://10.2.1.7/repository

-- 
Fernando Ney

How to change the copyright info for a site build?

[Wendell Beckwith]

When using the site:site goal how do I configure the copyright message 
that's added to all the pages (we're using APT)? This is important since 
management and legal get the willies just using open source let alone having 
that open source what is built as copyrighted by the Apache Software 
Foundation.

Wb

How to set a plugin's prefix?

[Wendell Beckwith]

I really hate to be dense, but I have created a settings.cml file with the 
following content and placed it in my .m2 directory, and the project itsself 
to no avail. I simply can't execute my plugin by the prefix. I looked at 
test it0031 and this provides no clues (for me at least) on how to configure 
this. Is there a better explanation or roadmap on how to achieve this 
behavior? If I need to actually debug maven to discover what is or isn't 
going on where do I start? What code should I be setting break points in?

Wb

Re: [m2] eclipse plugin breakage summary

[Ashley Williams]

Thanks, yes I managed to work out how to work locally on maven code -  
simple since they are all maven projects. Excellent!


Whether or not the eclipse plugin has bugs, I think my problem is  
actually how to persuade Eclipse to work with my file structure,  
because from what I can tell, you aren't supposed to link to file  
system directories that are above your Eclipse .classpath/.project  
files.


I'm actually trying to work with a single source tree by placing a  
pom in every package that I consider to be an artifact. Here is the  
directory structure I am working with (enlarge your mail message to  
prevent line wrap)


/Users/Developers/java-repository/
[pom.xml]

com/acme/proj1/
[MyClass1.java, MyClass2.java,  
pom.xml, .classpath, .project]


com/acme/proj2/
[MyClass3.java, MyClass4.java,  
pom.xml, .classpath, .project]


This works fine and so far I can do everything I want with the m2  
tool. However the problem comes when I try to make an eclipse project  
out of it, even editing the .classpath file by hand. It seems that  
the highest directory I'm supposed to include is the same as  
the .classpath file parent itself, when what I really want is a few  
directories above so that the classes start off in the com...  
package. Any lower then I get eclipse errors.


Any ideas?

Thanks
- AW

On 2 Sep 2005, at 20:27, Kenney Westerhof wrote:


On Fri, 2 Sep 2005, Ashley Williams wrote:

Hi,

first on your previous mail (one of them anyway): a local fix
is easy, if you have the plugin checked out and your m2 is
beta-1-SNAPSHOT. Just fix it and run m2 install.



Ok I get four different types of behaviour in eclipse depending on
what text I put in sourceDirectory after running eclipse:eclipse

 - StringIndexOutOfBoundsException
running eclipse:eclipse



I can imagine why.. Are your sources really in the same directory as
where your pom.xml is? I.e.

projectdir/pom.xml
projectdir/com/yourcompany/SourceFile.java

? Eclipse won't like that!

Anyway, fixed in svn HEAD.



. - sources in default package,
dependency libs are ther



Works for me.If sources are in the default package that means that  
they

don't have a 'package' declaration. Else eclipse would warn about
the package declaration not matching the source location.



/ - no package, no dependcy libs,
java files directly under project root icon



Correct. Sources are expected in / but there aren't any.
The rest of the files in the dir where .classpath and .project are
are considered normal files, not marked as source. This is expected.



\\ - no package yes depency libs,
java files directly under project root icon



Same here. \ gets replaced with /.



Which is the syntax I should be using anyway?



the relative path to the directory where your package structure  
begins.

'.' was ok.


-- Kenney




On 2 Sep 2005, at 17:32, Ashley Williams wrote:



Actually forget my last comment I've just seen that eclipse:eclipse
fails in the same way in the following method:

private static String toRelative( File basedir, String
absolutePath )
{
String relative;

if ( absolutePath.startsWith( basedir.getAbsolutePath() ) )
{
JUST HERE>>>relative = absolutePath.substring
( basedir.getAbsolutePath().length() + 1 );
}
else
{
relative = absolutePath;
}

relative = StringUtils.replace( relative, "\\", "/" );

return relative;
}

exception is java.lang.StringIndexOutOfBoundsException: String
index out of range: -1

Also if I wanted to do a local fix, how easy is it to build the
eclipse plugin on its own and get it into my repository??

Thanks
- AW



On 2 Sep 2005, at 17:17, Ashley Williams wrote:




Ok the latest maven seems to work despite the build exception and
happily I was able to run the eclipse:eclipse goal successfully.
However when I open the project in eclipse the files appear under
the (default package) node which means eclipse red crosses
everywhere. This despite the fact that the source code was created
under com.blah and installed okay.


On 2 Sep 2005, at 16:27, Ashley Williams wrote:





Oh happy day - not!

Just had a glance at my console only to see the pasted text below
- is this going to be a build breaker? I'm using Java 5 by
default, is this a mistake?? Also Mac OS X doesn't appear to have
a tools.jar file.



COPY AND PASTE...
Running maven-core integration tests ...

Using default local repository: /Users/developer/.m2/repository
it0063... FAILED
- Standard Out -
Command: /Applications/maven-latest/bin/m2 -e --no-plugin-
registry --batch-mode -Dmaven.repo.local=/Users/developer/.m2/
repository clean:clean package

- Standard Error -
Exit code: 1



Error Stacktrace:


org.apache.maven.it.VerificationException
at org.apache.maven.it.Verifier.executeGoals
(Verifier.java:574)
at org.apache.maven.it.Verif

Re: FW: [m2] war plug-in does not pay attention to dependency scoping

[Jesse McConnell]

are you certain that you are not bringing in the dependency from another one 
that you are sucking into the war?

use -X to get a breakdown of the dependency tree and maybe even paste that 
into here...

On 9/2/05, Michael Cassidy <[EMAIL PROTECTED]> wrote:
> 
> > I am using m2 (alpha2-3) to build a war. I have included scoping
> > information on dependencies, but they still end up in the war. Anyone
> > have an idea how to fix this. Pom excerpt below...
> >
> > 
> > tomcat-common-lib
> > _env-sb-concierge-tomcat
> > 0.0
> > provided
> > 
> >
> >
> > Michael D. Cassidy
> > Software Architect
> > Vegas.com 
> > [EMAIL PROTECTED]
> >
> 
> 


-- 
jesse mcconnell

RE: [m2] eclipse plugin breakage summary

[Lucas Javier Bernardi]

Hi guys
I need to customize the dir where test reports are placed, does any body
know how?

One more, how can I reference to the src dir from maven.xml, the property
does not work...

Help please
thanks
Lucas


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

Re: [m2] eclipse plugin breakage summary

[Kenney Westerhof]

On Fri, 2 Sep 2005, Ashley Williams wrote:

Hi,

first on your previous mail (one of them anyway): a local fix
is easy, if you have the plugin checked out and your m2 is
beta-1-SNAPSHOT. Just fix it and run m2 install.

> Ok I get four different types of behaviour in eclipse depending on
> what text I put in sourceDirectory after running eclipse:eclipse
>
>  - StringIndexOutOfBoundsException
> running eclipse:eclipse

I can imagine why.. Are your sources really in the same directory as
where your pom.xml is? I.e.

projectdir/pom.xml
projectdir/com/yourcompany/SourceFile.java

? Eclipse won't like that!

Anyway, fixed in svn HEAD.

> . - sources in default package,
> dependency libs are ther

Works for me.If sources are in the default package that means that they
don't have a 'package' declaration. Else eclipse would warn about
the package declaration not matching the source location.

> / - no package, no dependcy libs,
> java files directly under project root icon

Correct. Sources are expected in / but there aren't any.
The rest of the files in the dir where .classpath and .project are
are considered normal files, not marked as source. This is expected.

> \\ - no package yes depency libs,
> java files directly under project root icon

Same here. \ gets replaced with /.

> Which is the syntax I should be using anyway?

the relative path to the directory where your package structure begins.
'.' was ok.


-- Kenney

>
> On 2 Sep 2005, at 17:32, Ashley Williams wrote:
>
> > Actually forget my last comment I've just seen that eclipse:eclipse
> > fails in the same way in the following method:
> >
> > private static String toRelative( File basedir, String
> > absolutePath )
> > {
> > String relative;
> >
> > if ( absolutePath.startsWith( basedir.getAbsolutePath() ) )
> > {
> > JUST HERE>>>relative = absolutePath.substring
> > ( basedir.getAbsolutePath().length() + 1 );
> > }
> > else
> > {
> > relative = absolutePath;
> > }
> >
> > relative = StringUtils.replace( relative, "\\", "/" );
> >
> > return relative;
> > }
> >
> > exception is java.lang.StringIndexOutOfBoundsException: String
> > index out of range: -1
> >
> > Also if I wanted to do a local fix, how easy is it to build the
> > eclipse plugin on its own and get it into my repository??
> >
> > Thanks
> > - AW
> >
> >
> >
> > On 2 Sep 2005, at 17:17, Ashley Williams wrote:
> >
> >
> >> Ok the latest maven seems to work despite the build exception and
> >> happily I was able to run the eclipse:eclipse goal successfully.
> >> However when I open the project in eclipse the files appear under
> >> the (default package) node which means eclipse red crosses
> >> everywhere. This despite the fact that the source code was created
> >> under com.blah and installed okay.
> >>
> >>
> >> On 2 Sep 2005, at 16:27, Ashley Williams wrote:
> >>
> >>
> >>
> >>> Oh happy day - not!
> >>>
> >>> Just had a glance at my console only to see the pasted text below
> >>> - is this going to be a build breaker? I'm using Java 5 by
> >>> default, is this a mistake?? Also Mac OS X doesn't appear to have
> >>> a tools.jar file.
> >>>
> >>>
> >>>
> >>> COPY AND PASTE...
> >>> Running maven-core integration tests ...
> >>>
> >>> Using default local repository: /Users/developer/.m2/repository
> >>> it0063... FAILED
> >>> - Standard Out -
> >>> Command: /Applications/maven-latest/bin/m2 -e --no-plugin-
> >>> registry --batch-mode -Dmaven.repo.local=/Users/developer/.m2/
> >>> repository clean:clean package
> >>>
> >>> - Standard Error -
> >>> Exit code: 1
> >>>
> >>> >> Error Stacktrace:
> >>> org.apache.maven.it.VerificationException
> >>> at org.apache.maven.it.Verifier.executeGoals
> >>> (Verifier.java:574)
> >>> at org.apache.maven.it.Verifier.main(Verifier.java:677)
> >>> << Error Stacktrace
> >>> Log file contents:
> >>> + Error stacktraces are turned on.
> >>> [INFO] Searching repository for plugin with prefix: 'clean'.
> >>> [INFO]
> >>> 
> >>> 
> >>> [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0
> >>> [INFO]task-segment: [clean:clean, package]
> >>> [INFO]
> >>> 
> >>> 
> >>> [INFO] [clean:clean]
> >>> [INFO] [resources:resources]
> >>> [INFO]
> >>> 
> >>> 
> >>> [INFO] BUILD FAILURE
> >>> [INFO]
> >>> 
> >>> 
> >>> [INFO] Main Error:
> >>>   System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in
> >>> path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/
> >>> Home/../lib/tools.jar
> >>>   jdk-tools:jdk-tools:1.4.2:jar
> >>>
> >>> Path to dependency:
> >>> 1) org.apache.maven.it:maven-c

RE : Entity Expansion Limit Error

[Pascal Larin]

Michael,

Add -DentityExpansionLimit=10 (or more) to your MAVEN_OPTS.

Pascal

-Message d'origine-
De : Michael Owen [mailto:[EMAIL PROTECTED] 
Envoyé : September 2, 2005 14:35
À : users@maven.apache.org
Objet : Entity Expansion Limit Error

Hi,

Using Maven 1.1 beta and got the following error when running a multiproject

site goal on a large project:

BUILD FAILED
File.. C:\Documents and 
Settings\mike\.maven\cache\maven-multiproject-plugi
n-1.4.1\plugin.jelly
Element... maven:reactor
Line.. 104
Column -1
Unable to obtain goal [site] -- C:\Documents and 
Settings\mike\.maven\cache\mav
en-xdoc-plugin-1.9.1\plugin.jelly:122:-1:  Error on line 104797 of 
docu
ment  : Parser has reached the entity expansion limit "64,000" set by the 
Applic
ation. Nested exception: Parser has reached the entity expansion limit 
"64,000"
set by the Application.
Total time   : 6 minutes 33 seconds

Anyway I can get around it by increasing the expansion limit or something 
similar?

Thanks,

Mike



-
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]

FW: [m2] war plug-in does not pay attention to dependency scoping

[Michael Cassidy]

> I am using m2 (alpha2-3) to build a war.  I have included scoping
> information on dependencies, but they still end up in the war.  Anyone
> have an idea how to fix this.  Pom excerpt below...
> 
> 
>   tomcat-common-lib
>   _env-sb-concierge-tomcat
>   0.0
>   provided
> 
> 
> 
> Michael D. Cassidy
> Software Architect
> Vegas.com
> [EMAIL PROTECTED]
> 

Entity Expansion Limit Error

[Michael Owen]

Hi,

Using Maven 1.1 beta and got the following error when running a multiproject 
site goal on a large project:


BUILD FAILED
File.. C:\Documents and 
Settings\mike\.maven\cache\maven-multiproject-plugi

n-1.4.1\plugin.jelly
Element... maven:reactor
Line.. 104
Column -1
Unable to obtain goal [site] -- C:\Documents and 
Settings\mike\.maven\cache\mav
en-xdoc-plugin-1.9.1\plugin.jelly:122:-1:  Error on line 104797 of 
docu
ment  : Parser has reached the entity expansion limit "64,000" set by the 
Applic
ation. Nested exception: Parser has reached the entity expansion limit 
"64,000"

set by the Application.
Total time   : 6 minutes 33 seconds

Anyway I can get around it by increasing the expansion limit or something 
similar?


Thanks,

Mike



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

Findbugs plugin

[Colin Chalmers]

Hi all,

I started looking into the finbugs plugin today on Maven 1.0.2. 
Unfortunately I'm getting the following error.
Is anyone using this plugin successfully and/or have come across this 
error before?


/colin

*'D:\devtools\maven\core-subproject\target\classes'*
*The ' characters around the executable and arguments are
not part of the command.*
*[findbugs] java.lang.VerifyError: Cannot inherit from final class
   [findbugs]  at java.lang.ClassLoader.defineClass0(Native Method)
   [findbugs]  at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
   [findbugs]  at 
java.security.SecureClassLoader.defineClass(SecureClassLoader

.java:123)
   [findbugs]  at 
java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
   [findbugs]  at 
java.net.URLClassLoader.access$100(URLClassLoader.java:55)

   [findbugs]  at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
   [findbugs]  at java.security.AccessController.doPrivileged(Native 
Method)
   [findbugs]  at 
java.net.URLClassLoader.findClass(URLClassLoader.java:187)

   [findbugs]  at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
   [findbugs]  at 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)*

*[findbugs]  at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
   [findbugs]  at 
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)*

*[findbugs]  at java.lang.Class.getDeclaredMethods0(Native Method)
   [findbugs]  at 
java.lang.Class.privateGetDeclaredMethods(Class.java:1655)

   [findbugs]  at java.lang.Class.getDeclaredMethod(Class.java:1262)
   [findbugs]  at 
edu.umd.cs.findbugs.DetectorFactory.(DetectorFactory.ja

va:77)
   [findbugs]  at 
edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:202)
   [findbugs]  at 
edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:88)*
*[findbugs]  at 
edu.umd.cs.findbugs.DetectorFactoryCollection.loadPlugins(Det

ectorFactoryCollection.java:187)
   [findbugs]  at 
edu.umd.cs.findbugs.DetectorFactoryCollection.(Detector

FactoryCollection.java:50)
   [findbugs]  at 
edu.umd.cs.findbugs.DetectorFactoryCollection.instance(Detect

orFactoryCollection.java:71)
   [findbugs]  at 
edu.umd.cs.findbugs.FindBugs.createExecutionPlan(FindBugs.jav

a:1207)
   [findbugs]  at edu.umd.cs.findbugs.FindBugs.execute(FindBugs.java:1039)
   [findbugs]  at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:1726)
   [findbugs]  at edu.umd.cs.findbugs.FindBugs.main(FindBugs.java:1658)
   [findbugs] Exception in thread "main"
   [findbugs] Output saved to 
D:\devtools\maven\core-subproject/target/findbugs

-raw-report.xml*


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

Re: [m2] eclipse plugin breakage summary

[Ashley Williams]

Ok I get four different types of behaviour in eclipse depending on  
what text I put in sourceDirectory after running eclipse:eclipse


 - StringIndexOutOfBoundsException  
running eclipse:eclipse
. - sources in default package,  
dependency libs are ther
/ - no package, no dependcy libs,  
java files directly under project root icon
\\ - no package yes depency libs,  
java files directly under project root icon


Which is the syntax I should be using anyway?

On 2 Sep 2005, at 17:32, Ashley Williams wrote:

Actually forget my last comment I've just seen that eclipse:eclipse  
fails in the same way in the following method:


private static String toRelative( File basedir, String  
absolutePath )

{
String relative;

if ( absolutePath.startsWith( basedir.getAbsolutePath() ) )
{
JUST HERE>>>relative = absolutePath.substring 
( basedir.getAbsolutePath().length() + 1 );

}
else
{
relative = absolutePath;
}

relative = StringUtils.replace( relative, "\\", "/" );

return relative;
}

exception is java.lang.StringIndexOutOfBoundsException: String  
index out of range: -1


Also if I wanted to do a local fix, how easy is it to build the  
eclipse plugin on its own and get it into my repository??


Thanks
- AW



On 2 Sep 2005, at 17:17, Ashley Williams wrote:


Ok the latest maven seems to work despite the build exception and  
happily I was able to run the eclipse:eclipse goal successfully.  
However when I open the project in eclipse the files appear under  
the (default package) node which means eclipse red crosses  
everywhere. This despite the fact that the source code was created  
under com.blah and installed okay.



On 2 Sep 2005, at 16:27, Ashley Williams wrote:




Oh happy day - not!

Just had a glance at my console only to see the pasted text below  
- is this going to be a build breaker? I'm using Java 5 by  
default, is this a mistake?? Also Mac OS X doesn't appear to have  
a tools.jar file.




COPY AND PASTE...
Running maven-core integration tests ...

Using default local repository: /Users/developer/.m2/repository
it0063... FAILED
- Standard Out -
Command: /Applications/maven-latest/bin/m2 -e --no-plugin- 
registry --batch-mode -Dmaven.repo.local=/Users/developer/.m2/ 
repository clean:clean package


- Standard Error -
Exit code: 1

>> Error Stacktrace:
org.apache.maven.it.VerificationException
at org.apache.maven.it.Verifier.executeGoals 
(Verifier.java:574)

at org.apache.maven.it.Verifier.main(Verifier.java:677)
<< Error Stacktrace
Log file contents:
+ Error stacktraces are turned on.
[INFO] Searching repository for plugin with prefix: 'clean'.
[INFO]  
 


[INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0
[INFO]task-segment: [clean:clean, package]
[INFO]  
 


[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO]  
 


[INFO] BUILD FAILURE
[INFO]  
 


[INFO] Main Error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



Root error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



On 2 Sep 2005, at 15:52, Trygve Laugstøl wrote:





On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:




Don't understand what you're saying the problem is, but will  
the fix

be quick, i.e. 10 minutes?? If so then I don't mind waiting...






Try now.

--
Trygve







 
-

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: [m2] eclipse plugin broken (sorry,still in the same way)

[Ashley Williams]

Actually forget my last comment I've just seen that eclipse:eclipse  
fails in the same way in the following method:


private static String toRelative( File basedir, String  
absolutePath )

{
String relative;

if ( absolutePath.startsWith( basedir.getAbsolutePath() ) )
{
JUST HERE>>>relative = absolutePath.substring 
( basedir.getAbsolutePath().length() + 1 );

}
else
{
relative = absolutePath;
}

relative = StringUtils.replace( relative, "\\", "/" );

return relative;
}

exception is java.lang.StringIndexOutOfBoundsException: String index  
out of range: -1


Also if I wanted to do a local fix, how easy is it to build the  
eclipse plugin on its own and get it into my repository??


Thanks
- AW



On 2 Sep 2005, at 17:17, Ashley Williams wrote:

Ok the latest maven seems to work despite the build exception and  
happily I was able to run the eclipse:eclipse goal successfully.  
However when I open the project in eclipse the files appear under  
the (default package) node which means eclipse red crosses  
everywhere. This despite the fact that the source code was created  
under com.blah and installed okay.



On 2 Sep 2005, at 16:27, Ashley Williams wrote:



Oh happy day - not!

Just had a glance at my console only to see the pasted text below  
- is this going to be a build breaker? I'm using Java 5 by  
default, is this a mistake?? Also Mac OS X doesn't appear to have  
a tools.jar file.




COPY AND PASTE...
Running maven-core integration tests ...

Using default local repository: /Users/developer/.m2/repository
it0063... FAILED
- Standard Out -
Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry  
--batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository  
clean:clean package


- Standard Error -
Exit code: 1

>> Error Stacktrace:
org.apache.maven.it.VerificationException
at org.apache.maven.it.Verifier.executeGoals(Verifier.java: 
574)

at org.apache.maven.it.Verifier.main(Verifier.java:677)
<< Error Stacktrace
Log file contents:
+ Error stacktraces are turned on.
[INFO] Searching repository for plugin with prefix: 'clean'.
[INFO]  
- 
---

[INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0
[INFO]task-segment: [clean:clean, package]
[INFO]  
- 
---

[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO]  
- 
---

[INFO] BUILD FAILURE
[INFO]  
- 
---

[INFO] Main Error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



Root error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



On 2 Sep 2005, at 15:52, Trygve Laugstøl wrote:




On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:



Don't understand what you're saying the problem is, but will the  
fix

be quick, i.e. 10 minutes?? If so then I don't mind waiting...





Try now.

--
Trygve






-
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] eclipse plugin broken in a different way

[Ashley Williams]

Ok the latest maven seems to work despite the build exception and  
happily I was able to run the eclipse:eclipse goal successfully.  
However when I open the project in eclipse the files appear under the  
(default package) node which means eclipse red crosses everywhere.  
This despite the fact that the source code was created under  
com.blah and installed okay.



On 2 Sep 2005, at 16:27, Ashley Williams wrote:


Oh happy day - not!

Just had a glance at my console only to see the pasted text below -  
is this going to be a build breaker? I'm using Java 5 by default,  
is this a mistake?? Also Mac OS X doesn't appear to have a  
tools.jar file.




COPY AND PASTE...
Running maven-core integration tests ...

Using default local repository: /Users/developer/.m2/repository
it0063... FAILED
- Standard Out -
Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry  
--batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository  
clean:clean package


- Standard Error -
Exit code: 1

>> Error Stacktrace:
org.apache.maven.it.VerificationException
at org.apache.maven.it.Verifier.executeGoals(Verifier.java: 
574)

at org.apache.maven.it.Verifier.main(Verifier.java:677)
<< Error Stacktrace
Log file contents:
+ Error stacktraces are turned on.
[INFO] Searching repository for plugin with prefix: 'clean'.
[INFO]  
-- 
--

[INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0
[INFO]task-segment: [clean:clean, package]
[INFO]  
-- 
--

[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO]  
-- 
--

[INFO] BUILD FAILURE
[INFO]  
-- 
--

[INFO] Main Error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



Root error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in  
path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ 
Home/../lib/tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



On 2 Sep 2005, at 15:52, Trygve Laugstøl wrote:



On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:



Don't understand what you're saying the problem is, but will the fix
be quick, i.e. 10 minutes?? If so then I don't mind waiting...




Try now.

--
Trygve





-
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] I'm having a problem using the SCM plugin.

[eric . starr]

I am trying to create a pom.xml file for a project that will download the 
latest source from cvs.

  
scm:cvs:pserver:]::

  

Here is the command that I use to checkout the source:


C:\tmp\projects\project1>m2 scm:checkout
[INFO] Searching repository for plugin with prefix: 'scm'.
[WARNING]
  * Using defaults for missing POM 
org.apache.maven.plugins:maven-scm-plugin:pom:1.0-alpha-2-SNAPSHOT *
 
[INFO] Cannot find mojo descriptor for: 'scm:checkout' - Treating 
as non-aggregator.
[INFO] 

[INFO] Building project1
[INFO]task-segment: [scm:checkout]
[INFO] 

[INFO] Searching repository for plugin with prefix: 'scm'.
[WARNING]
  * Using defaults for missing POM 
org.apache.maven.plugins:maven-scm-plugin:pom:1.0-alpha-2-SNAPSHOT *
 
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Main Error:
  Mojo could not be found - check that the goal name is correct
 
org.apache.maven.plugins:maven-scm-plugin:1.0-alpha-2-SNAPSHOT:maven-plugin
 
from the specified remote repositories:
  http://repo1.maven.org/maven2/plugins
 
Root error:
  Unable to download the artifact from any repository
[INFO] 

[INFO] Total time: < 1 second
[INFO] Finished at: Fri Sep 02 12:03:35 EDT 2005
[INFO] Final Memory: 1M/2M
[INFO] 



I looked here to try to find the plugin, but I don't see it.  Any ideas?
 
http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/maven-scm-plugin/


Eric Starr

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

Re: Best practices for release and version management?

[Sanjay Choudhary]

Hi David,
 Is it possible for you to share the "internal process" document with us? It 
will help a lot.
 -Sanjay

 On 9/2/05, David Jackman <[EMAIL PROTECTED]> wrote: 
> 
> We're pretty much doing what Jose is doing, but we don't see these 
> timeouts. I think it's because the Maven properties are set up to look in 
> our internal repository first and then go global from there. Just about 
> everything is in the internal repository (certainly the artifacts for our 
> projects are there), so the download time isn't much at all.
> 
> My maven.repo.remote property lists the internal repository first, and 
> ibiblio second.
> 
> As far as the approach to take when releasing and incrementing versions, 
> the process you describe is essentially what we're doing. In fact, I just 
> wrote up a document outlining our internal process for releasing projects 
> for our developers (since we're about to release the big project soon), so I 
> know the details very well.
> 
> ..David..
> 
> 
> -Original Message-
> From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 02, 2005 4:14 AM
> To: Maven Users List
> Subject: Re: Best practices for release and version management?
> 
> On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> > Hi there,
> >
> > How do you use to manage your project version among releases? I
> > mean... what do you exactly put in currentVersion in your pom and how
> > do you change it among releases?
> >
> > I'm currently using the following approach:
> >
> > 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT 2. V0.1
> > release: commit all pending changes, change currentVersion to 0.1,
> > commit pom, tag/branch repository, make release.
> > 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT,
> > commit pom, update and continue developing
> 
> This is the way that we're recomending and using ourselfs.
> 
> > What do you think about this? This approach has one annoying thing:
> > maven tries to download SNAPSHOT versions from remote repositories,
> > although they're only locally installed in the developer repository.
> > After some timeout maven uses the local version, but in case of large
> > projects the sum of the timeouts may be big. Do you use any other
> > approach?
> 
> The easiest solution to this problem is to either configure a proxy so it 
> doesn't time out (but rather get a 404 response from the HTTP server) or 
> just run Maven in off-line mode (by using the -o switch)
> 
> --
> Trygve
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Re: [m1] Conditional dependencies

[Wendy Smoak]

From: "Brett Porter" <[EMAIL PROTECTED]>


This is a bit "dangerous".


Agreed. :)  But it works.


1) a project will have a different model depending on that property. It
will ripple into needing to change other things like the final name of the
built artifact to ensure you don't end up with one thing sometimes being
something different


Actually... that's the intent.  We build a .war file, and it contains
whichever JSF implementation you choose-- different .jar files in
WEB-INF/lib, web.xml filtered one way or another, but the name of the .war
file remains the same.  (Remember that this is an existing Ant build...)


This is a little bit of an unusual use case. It's understandable that you
often depend on a spec dependency (for which we don't yet have great
support) and an impl goes into the final bundle and the impl might change.
Changing the API too is what is unusual.


I agree... but that's the requirement.


Anyway, in m1 the general approach to this is to have two projects that do
the different bundling and build whichever you want, sharing the common
code. I'm not sure if that's easily done when the api is changed though.


I've just been introduced to the "leave the project structure alone and put
all the build files in a completely separate directory structure" concept.
Most of my problems (like building three artifacts out of a single source
tree) might just go away.  Reorganizing the project itself to suit Maven is
definitely not something I want to have to push for.


I replied in this fashion in another thread. I should also mention again
that environmental changes to project builds are supported in Maven 2.


(I missed your earlier responses, thanks for pointing them out.)  Okay,
okay... I'll look at m2 again.  :)  Last time it seemed like not enough of
the plugins I needed were ready yet.

--
Wendy


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

Re: [m2] eclipse plugin exception

[Ashley Williams]

Oh happy day - not!

Just had a glance at my console only to see the pasted text below -  
is this going to be a build breaker? I'm using Java 5 by default, is  
this a mistake?? Also Mac OS X doesn't appear to have a tools.jar file.




COPY AND PASTE...
Running maven-core integration tests ...

Using default local repository: /Users/developer/.m2/repository
it0063... FAILED
- Standard Out -
Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- 
batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository  
clean:clean package


- Standard Error -
Exit code: 1

>> Error Stacktrace:
org.apache.maven.it.VerificationException
at org.apache.maven.it.Verifier.executeGoals(Verifier.java:574)
at org.apache.maven.it.Verifier.main(Verifier.java:677)
<< Error Stacktrace
Log file contents:
+ Error stacktraces are turned on.
[INFO] Searching repository for plugin with prefix: 'clean'.
[INFO]  
 


[INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0
[INFO]task-segment: [clean:clean, package]
[INFO]  
 


[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO]  
 


[INFO] BUILD FAILURE
[INFO]  
 


[INFO] Main Error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / 
System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/../lib/ 
tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



Root error:
  System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / 
System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/../lib/ 
tools.jar

  jdk-tools:jdk-tools:1.4.2:jar

Path to dependency:
1) org.apache.maven.it:maven-core-it0063:jar:1.0
2) jdk-tools:jdk-tools:jar:1.4.2



On 2 Sep 2005, at 15:52, Trygve Laugstøl wrote:


On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:


Don't understand what you're saying the problem is, but will the fix
be quick, i.e. 10 minutes?? If so then I don't mind waiting...



Try now.

--
Trygve




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

Re: Best practices for release and version management?

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 10:54:37AM -0400, dohadwala, moiz wrote:
> How does one do it for m2?
> 
> I am new to maven and I have decided to skip maven 1.x and start with m2
> directly.

In Maven 2 there is the same off-line option as in Maven 1 but you can
also say that repositories can contain snapshots or not so by default
Maven won't go to Ibiblio to look for snapshots.

--
Trygve


signature.asc
Description: Digital signature

RE: Best practices for release and version management?

[dohadwala, moiz]

How does one do it for m2?

I am new to maven and I have decided to skip maven 1.x and start with m2
directly.

-Moiz 

-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 02, 2005 7:00 AM
To: Maven Users List
Subject: RE: Best practices for release and version management?

We're pretty much doing what Jose is doing, but we don't see these timeouts.
I think it's because the Maven properties are set up to look in our internal
repository first and then go global from there.  Just about everything is in
the internal repository (certainly the artifacts for our projects are
there), so the download time isn't much at all.

My maven.repo.remote property lists the internal repository first, and
ibiblio second.

As far as the approach to take when releasing and incrementing versions, the
process you describe is essentially what we're doing.  In fact, I just wrote
up a document outlining our internal process for releasing projects for our
developers (since we're about to release the big project soon), so I know
the details very well.

..David..
 

-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, September 02, 2005 4:14 AM
To: Maven Users List
Subject: Re: Best practices for release and version management?

On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> Hi there,
> 
> How do you use to manage your project version among releases? I 
> mean... what do you exactly put in currentVersion in your pom and how 
> do you change it among releases?
> 
> I'm currently using the following approach:
> 
> 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT 2. V0.1
> release: commit all pending changes, change currentVersion to 0.1, 
> commit pom, tag/branch repository, make release.
> 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT, 
> commit pom, update and continue developing

This is the way that we're recomending and using ourselfs.

> What do you think about this? This approach has one annoying thing:
> maven tries to download SNAPSHOT versions from remote repositories, 
> although they're only locally installed in the developer repository.
> After some timeout maven uses the local version, but in case of large 
> projects the sum of the timeouts may be big. Do you use any other 
> approach?

The easiest solution to this problem is to either configure a proxy so it
doesn't time out (but rather get a 404 response from the HTTP server) or
just run Maven in off-line mode (by using the -o switch)

--
Trygve

-
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] eclipse plugin exception

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 03:34:59PM +0100, Ashley Williams wrote:
> Don't understand what you're saying the problem is, but will the fix  
> be quick, i.e. 10 minutes?? If so then I don't mind waiting...

Try now.

--
Trygve


signature.asc
Description: Digital signature

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Jörg Schaible]

Martin Burger wrote on Friday, September 02, 2005 4:45 PM:

> Jörg Schaible schrieb am 02.09.2005 16:00:
> 
>> Just start a remote command:
>> 
>> plink -A -2 -ssh [EMAIL PROTECTED] ls -l
>> 
>> This should give you a list of your home directory on the remote
>> server. You should not have to press any key or logout manually.
>> 
> 
> Strange.
> 
>  >plink.exe -A -2 -ssh [EMAIL PROTECTED] ls -l
> 
> That causes a zombie process. After killing the process, the command
> works. If I want to list another dir, zombie process again. After
> killing that process, I can list that second dir. So, sometimes it
> works, sometimes not. Any idea?

No, not really. You might ask a SysAdmin. But as long as it behaves in this 
way, Maven will not do better.

- Jörg

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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Jörg Schaible schrieb am 02.09.2005 16:00:


Just start a remote command:

plink -A -2 -ssh [EMAIL PROTECTED] ls -l

This should give you a list of your home directory on the remote server. You 
should not have to press any key or logout manually.



Strange.

>plink.exe -A -2 -ssh [EMAIL PROTECTED] ls -l

That causes a zombie process. After killing the process, the command 
works. If I want to list another dir, zombie process again. After 
killing that process, I can list that second dir. So, sometimes it 
works, sometimes not. Any idea?


Regards, Martin

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

Re: [m2] eclipse plugin exception

[Ashley Williams]

Don't understand what you're saying the problem is, but will the fix  
be quick, i.e. 10 minutes?? If so then I don't mind waiting...



On 2 Sep 2005, at 15:31, Trygve Laugstøl wrote:


On Fri, Sep 02, 2005 at 03:27:04PM +0100, Ashley Williams wrote:


Build has failed - it's never easy is it!



Sorry about that, I'm fixing that any second now. It got past our  
CI as

only do a clean build once per night.

You can download the latest Maven 2 snapshot from [1].

[1]: http://maven.zones.apache.org/~maven/builds/ 
m2-20050902.104500.tar.gz


--
Trygve




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

Re: [m2] eclipse plugin exception

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 03:27:04PM +0100, Ashley Williams wrote:
> Build has failed - it's never easy is it!

Sorry about that, I'm fixing that any second now. It got past our CI as
only do a clean build once per night.

You can download the latest Maven 2 snapshot from [1].

[1]: http://maven.zones.apache.org/~maven/builds/m2-20050902.104500.tar.gz

--
Trygve


signature.asc
Description: Digital signature

Re: [m2] eclipse plugin exception

[Ashley Williams]

Build has failed - it's never easy is it!

I made sure M2_HOME points to a non existent directory and added  
nonexistentdirectory/bin to my PATH. then I ran the script and  
eventually got this:


Building project in /Users/develop/projects/Burns/maven-components/ 
maven-artifact-manager ...


Building project in /Users/develop/projects/Burns/maven-components/ 
maven-artifact-manager
Error reading POM: /Users/develop/projects/Burns/maven-components/ 
maven-artifact-manager/pom.xml
Exception in thread "main" java.io.FileNotFoundException: /Users/ 
develop/.m2/repository/org/apache/maven/maven-repository-metadata/2.0- 
beta-1-SNAPSHOT/maven-repository-metadata-2.0-beta-1-SNAPSHOT.pom (No  
such file or directory)

at model.ModelReader.retrievePom(ModelReader.java:485)
at model.ModelReader.resolveDependencies(ModelReader.java:412)
at model.ModelReader.endElement(ModelReader.java:384)
at  
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement( 
AbstractSAXParser.java:633)
at  
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s 
canEndElement(XMLDocumentFragmentScannerImpl.java:1241)
at  
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl 
$FragmentContentDispatcher.dispatch 
(XMLDocumentFragmentScannerImpl.java:1685)
at  
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s 
canDocument(XMLDocumentFragmentScannerImpl.java:368)
at  
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse 
(XML11Configuration.java:834)
at  
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse 
(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse 
(XMLParser.java:148)
at  
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse 
(AbstractSAXParser.java:1242)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at util.AbstractReader.parse(AbstractReader.java:63)
at MBoot.buildProject(MBoot.java:505)
at MBoot.run(MBoot.java:349)
at MBoot.main(MBoot.java:121)


Also at the start of the build I got this warning which seems to  
suggest I need a previous installation of maven:


Building mboot ...
---
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
---
Building maven2 components ...
---
You SHOULD have a ~/.m2/settings.xml file and must contain at least  
the following information:



  /path/to/your/repository


Alternatively, you can specify -Dmaven.repo.local=/path/to/m2/repository


On 2 Sep 2005, at 15:14, Trygve Laugstøl wrote:


On Fri, Sep 02, 2005 at 03:08:30PM +0100, Ashley Williams wrote:


No that didn't work either. In fact I tried a large nonsense string
too and that also resulted in the very same exception, which
surprised me. I've just downloaded the maven source code so I'll
check if I still get the same behaviour.



Ok, thanks.

The code you're looking for is under maven-plugins/maven-eclipse- 
plugin.

Please read [1] for information on how to build Maven.

[1]: http://maven.apache.org/maven2/developers/building.html

--
Trygve




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

Re: [m2] eclipse plugin exception

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 03:08:30PM +0100, Ashley Williams wrote:
> No that didn't work either. In fact I tried a large nonsense string  
> too and that also resulted in the very same exception, which  
> surprised me. I've just downloaded the maven source code so I'll  
> check if I still get the same behaviour.

Ok, thanks.

The code you're looking for is under maven-plugins/maven-eclipse-plugin.
Please read [1] for information on how to build Maven.

[1]: http://maven.apache.org/maven2/developers/building.html

--
Trygve


signature.asc
Description: Digital signature

Re: [m2] eclipse plugin exception

[Ashley Williams]

No that didn't work either. In fact I tried a large nonsense string  
too and that also resulted in the very same exception, which  
surprised me. I've just downloaded the maven source code so I'll  
check if I still get the same behaviour.


On 2 Sep 2005, at 14:52, Trygve Laugstøl wrote:


On Fri, Sep 02, 2005 at 02:47:35PM +0100, Ashley Williams wrote:


Hi, I'm trying to configure my source directory to be the current
directory like so:

attempt 1:
  


attempt 2:
  
/



Try ".".




which works fine. The problem is when I subsequently run the
eclipse:eclipse goal, which in both cases results in the following
exception:

java.lang.StringIndexOutOfBoundsException: String index out of  
range: -1

at java.lang.String.substring(String.java:1768)
at java.lang.String.substring(String.java:1735)
at org.apache.maven.plugin.eclipse.EclipseWriter.toRelative
(EclipseWriter.java:362)
at
org.apache.maven.plugin.eclipse.EclipseWriter.addSourceRoots
(EclipseWriter.java:262)
at
org.apache.maven.plugin.eclipse.EclipseWriter.writeEclipseClasspath
(EclipseWriter.java:180)
at org.apache.maven.plugin.eclipse.EclipseWriter.write
(EclipseWriter.java:64)
at org.apache.maven.plugin.eclipse.EclipsePlugin.execute
(EclipsePlugin.java:100)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:401)

Without having the sourcecode I can sort of guess that the empty path
would give it problems, but does anybody know if this is fixed in the
forthcoming beta?



This looks like a bug, please file it in jira[1] under 'maven- 
plugins'.


[1]: http://jira.codehaus.org/browse/MNG

--
Trygve




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

Re: [m2] eclipse plugin exception

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 02:47:35PM +0100, Ashley Williams wrote:
> Hi, I'm trying to configure my source directory to be the current  
> directory like so:
> 
> attempt 1:
>   
> 
> 
> attempt 2:
>   
> /

Try ".".

> 
> which works fine. The problem is when I subsequently run the  
> eclipse:eclipse goal, which in both cases results in the following  
> exception:
> 
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at java.lang.String.substring(String.java:1735)
> at org.apache.maven.plugin.eclipse.EclipseWriter.toRelative 
> (EclipseWriter.java:362)
> at  
> org.apache.maven.plugin.eclipse.EclipseWriter.addSourceRoots 
> (EclipseWriter.java:262)
> at  
> org.apache.maven.plugin.eclipse.EclipseWriter.writeEclipseClasspath 
> (EclipseWriter.java:180)
> at org.apache.maven.plugin.eclipse.EclipseWriter.write 
> (EclipseWriter.java:64)
> at org.apache.maven.plugin.eclipse.EclipsePlugin.execute 
> (EclipsePlugin.java:100)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
> (DefaultPluginManager.java:401)
> 
> Without having the sourcecode I can sort of guess that the empty path  
> would give it problems, but does anybody know if this is fixed in the  
> forthcoming beta?

This looks like a bug, please file it in jira[1] under 'maven-plugins'.

[1]: http://jira.codehaus.org/browse/MNG

--
Trygve


signature.asc
Description: Digital signature

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Jörg Schaible]

Martin Burger wrote on Friday, September 02, 2005 3:35 PM:

> Jörg Schaible schrieb am 02.09.2005 15:06:
> 
>> What happens if you start plink manually (with the options from the
>> Maven proeprties file) 
>> 
> 
>  >C:\\Programme\\INet\\Remote\\PuTTY\\plink.exe -A -2 -ssh
> [EMAIL PROTECTED] Using username "auser".

Just start a remote command:

plink -A -2 -ssh [EMAIL PROTECTED] ls -l

This should give you a list of your home directory on the remote server. You 
should not have to press any key or logout manually.

- Jörg

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

RE: Best practices for release and version management?

[David Jackman]

We're pretty much doing what Jose is doing, but we don't see these timeouts.  I 
think it's because the Maven properties are set up to look in our internal 
repository first and then go global from there.  Just about everything is in 
the internal repository (certainly the artifacts for our projects are there), 
so the download time isn't much at all.

My maven.repo.remote property lists the internal repository first, and ibiblio 
second.

As far as the approach to take when releasing and incrementing versions, the 
process you describe is essentially what we're doing.  In fact, I just wrote up 
a document outlining our internal process for releasing projects for our 
developers (since we're about to release the big project soon), so I know the 
details very well.

..David..
 

-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 02, 2005 4:14 AM
To: Maven Users List
Subject: Re: Best practices for release and version management?

On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> Hi there,
> 
> How do you use to manage your project version among releases? I 
> mean... what do you exactly put in currentVersion in your pom and how 
> do you change it among releases?
> 
> I'm currently using the following approach:
> 
> 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT 2. V0.1 
> release: commit all pending changes, change currentVersion to 0.1, 
> commit pom, tag/branch repository, make release.
> 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT, 
> commit pom, update and continue developing

This is the way that we're recomending and using ourselfs.

> What do you think about this? This approach has one annoying thing:
> maven tries to download SNAPSHOT versions from remote repositories, 
> although they're only locally installed in the developer repository.
> After some timeout maven uses the local version, but in case of large 
> projects the sum of the timeouts may be big. Do you use any other 
> approach?

The easiest solution to this problem is to either configure a proxy so it 
doesn't time out (but rather get a 404 response from the HTTP server) or just 
run Maven in off-line mode (by using the -o switch)

--
Trygve

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

[m2] eclipse plugin exception

[Ashley Williams]

Hi, I'm trying to configure my source directory to be the current  
directory like so:


attempt 1:
  


attempt 2:
  
/

which works fine. The problem is when I subsequently run the  
eclipse:eclipse goal, which in both cases results in the following  
exception:


java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1768)
at java.lang.String.substring(String.java:1735)
at org.apache.maven.plugin.eclipse.EclipseWriter.toRelative 
(EclipseWriter.java:362)
at  
org.apache.maven.plugin.eclipse.EclipseWriter.addSourceRoots 
(EclipseWriter.java:262)
at  
org.apache.maven.plugin.eclipse.EclipseWriter.writeEclipseClasspath 
(EclipseWriter.java:180)
at org.apache.maven.plugin.eclipse.EclipseWriter.write 
(EclipseWriter.java:64)
at org.apache.maven.plugin.eclipse.EclipsePlugin.execute 
(EclipsePlugin.java:100)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPluginManager.java:401)


Without having the sourcecode I can sort of guess that the empty path  
would give it problems, but does anybody know if this is fixed in the  
forthcoming beta?


Thanks
-AW

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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Jörg Schaible schrieb am 02.09.2005 15:06:


What happens if you start plink manually (with the options from the Maven 
proeprties file)



>C:\\Programme\\INet\\Remote\\PuTTY\\plink.exe -A -2 -ssh 
[EMAIL PROTECTED]

Using username "auser".
Linux ahost 2.6.11.9-050512a #1 SMP Thu May 12 20:53:02 CEST 2005 i686 
GNU/Linux


The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.



Then the loudspeaker of my PC beeps and I have a login shell. There are 
some escape characters, but plinks spawn's the mkdir process, so I think 
these character should be no problem.


Regards,
   Martin

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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Jörg Schaible schrieb am 02.09.2005 15:06:


What happens if you start plink manually (with the options from the Maven 
proeprties file)?
Get the executed command from Maven by calling it with -X option.



Using -X option shows a lot of [DEBUG] messages, but no commands:

[DEBUG] Could not load class 
(org.apache.tools.ant.taskdefs.optional.ejb.DDCreator) for type ddcreator

   [echo] Deploying...
Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\Martin 
Burger\build.properties
Using projectPropertiesFile: 
E:\Uni\DiplInf\repository\trunk\ddchange-framework-debugging\project.properties
Using projectBuildPropertiesFile: 
E:\Uni\DiplInf\repository\trunk\ddchange-framework-debugging\build.properties

Will deploy to 1 repository(ies): ddchangerepo
Deploying to repository: ddchangerepo
Uploading to 
deltadebugging/poms/ddchange-framework-debugging-0.1.1-SNAPSHOT.pom:



Regards,
   Martin

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

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Jörg Schaible]

Martin Burger wrote on Friday, September 02, 2005 2:56 PM:

> Jörg Schaible schrieb am 02.09.2005 14:51:
>>> Well, IMHO, maven.repo.foorepo.ssh.executable and
>>> maven.repo.foorepo.scp.executable seem like they have to be
>>> Windows executables, since the jar has to be deployed from Windows to
>>> Linux...
>> 
>> 
>> OK, this is different. In that case I assume, that he had not started
>> the putty agent and Maven is waiting for manual input. 
> 
> No, plink causes the zombie processes. That means that it can connect
> the server. After killing some zombie processes, pscp copies the file
> to the server. After that there are again some zombie processes
> causesd by plink.  

What happens if you start plink manually (with the options from the Maven 
proeprties file)?
Get the executed command from Maven by calling it with -X option.

- Jörg

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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Martin Burger schrieb am 02.09.2005 14:53:

Because I deploy from a German Windows XP machine to a Debian box I 
expect that it works. ;-)



Uups, that does not mean that a German XP is better as another one. But 
perhaps the different languages on the systems cause the problem...


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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Jörg Schaible schrieb am 02.09.2005 14:51:

  
Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be
Windows executables, since the jar has to be deployed from Windows to
Linux... 

  
  
OK, this is different. In that case I assume, that he had not started the putty agent and Maven is waiting for manual input.


No, plink causes the zombie processes. That means that it can connect
the server. After killing some zombie processes, pscp copies the file
to the server. After that there are again some zombie processes causesd
by plink.

Regards,
    Martin


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

Re: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Jörg Schaible schrieb am 02.09.2005 14:42:


Well, yes. You execute Maven on Linux and expect it to respect DOS/Windows 
paths and executables. So what do you expect?



Because I deploy from a German Windows XP machine to a Debian box I 
expect that it works. ;-)


Regards,
Martin

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

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Jörg Schaible]

Yann Le Du wrote on Friday, September 02, 2005 2:48 PM:

> Well, IMHO, maven.repo.foorepo.ssh.executable and
> maven.repo.foorepo.scp.executable seem like they have to be
> Windows executables, since the jar has to be deployed from Windows to
> Linux... 

OK, this is different. In that case I assume, that he had not started the putty 
agent and Maven is waiting for manual input.

- Jörg

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

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Yann Le Du]

Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be Windows
executables, since the jar has to be deployed from Windows to Linux...


--- Jörg Schaible <[EMAIL PROTECTED]> a écrit :

> Martin Burger wrote on Friday, September 02, 2005 2:06 PM:
> 
> > Hello!
> > 
> > I want to deploy a jar to my remote repository. But the goal
> > jar:deploy hangs. On the linux machine (Debian Sarge) there are some
> > "zombie" / "defunct" processes. If I kill such a process, the goal
> > continues until
> > the next process hangs. The processes are "[mkdir] " and
> > "[chmod] ". 
> > 
> > Here's my configuration for the artifact plugin:
> > 
> > maven.repo.list=foorepo 
> > maven.repo.foorepo=scpexe://host.some.where
> > maven.repo.foorepo.username=auser
> > maven.repo.foorepo.directory=/tmp
> > maven.repo.foorepo.compress=true
> > maven.repo.foorepo.ssh.executable=C:\\Programme\\Remote\\PuTTY\\plink.exe
> > maven.repo.foorepo.ssh.args=-A -2 -ssh
> > maven.repo.foorepo.scp.executable=C:\\Programme\\Remote\\PuTTY\\pscp.exe
> > maven.repo.foorepo.scp.args=-2 
> >
> > Any ideas?
> 
> Well, yes. You execute Maven on Linux and expect it to respect DOS/Windows
> paths and executables. So what do you expect?
> 
> - Jörg
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 







___ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

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

RE: maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Jörg Schaible]

Martin Burger wrote on Friday, September 02, 2005 2:06 PM:

> Hello!
> 
> I want to deploy a jar to my remote repository. But the goal
> jar:deploy hangs. On the linux machine (Debian Sarge) there are some
> "zombie" / "defunct" processes. If I kill such a process, the goal
> continues until
> the next process hangs. The processes are "[mkdir] " and
> "[chmod] ". 
> 
> Here's my configuration for the artifact plugin:
> 
> maven.repo.list=foorepo 
> maven.repo.foorepo=scpexe://host.some.where
> maven.repo.foorepo.username=auser
> maven.repo.foorepo.directory=/tmp
> maven.repo.foorepo.compress=true
> maven.repo.foorepo.ssh.executable=C:\\Programme\\Remote\\PuTTY\\plink.exe
> maven.repo.foorepo.ssh.args=-A -2 -ssh
> maven.repo.foorepo.scp.executable=C:\\Programme\\Remote\\PuTTY\\pscp.exe
> maven.repo.foorepo.scp.args=-2 
>
> Any ideas?

Well, yes. You execute Maven on Linux and expect it to respect DOS/Windows 
paths and executables. So what do you expect?

- Jörg

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

maven jar:deploy hangs - zombie processes (mkdir and chmod)

[Martin Burger]

Hello!

I want to deploy a jar to my remote repository. But the goal jar:deploy 
hangs. On the linux machine (Debian Sarge) there are some "zombie" / 
"defunct" processes. If I kill such a process, the goal continues until 
the next process hangs. The processes are "[mkdir] " and 
"[chmod] ".


Here's my configuration for the artifact plugin:

maven.repo.list=foorepo
maven.repo.foorepo=scpexe://host.some.where
maven.repo.foorepo.username=auser
maven.repo.foorepo.directory=/tmp
maven.repo.foorepo.compress=true
maven.repo.foorepo.ssh.executable=C:\\Programme\\Remote\\PuTTY\\plink.exe
maven.repo.foorepo.ssh.args=-A -2 -ssh
maven.repo.foorepo.scp.executable=C:\\Programme\\Remote\\PuTTY\\pscp.exe
maven.repo.foorepo.scp.args=-2

Any ideas?

Regards,
Martin

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

RE: no reads from my own remote, but writes go ok.

[Peter Veentjer - Anchor Men]

I have added the http server and know it works.

It is quite stupid that maven doesn`t give any errors (but it doesn`t have an 
problem to crash all over the place in other parts). So guys.. Fix this peace 
of software so I can take it seriously. 

-Oorspronkelijk bericht-
Van: Lothar Märkle [mailto:[EMAIL PROTECTED] 
Verzonden: vrijdag 2 september 2005 13:32
Aan: Maven Users List
Onderwerp: Re: no reads from my own remote, but writes go ok.

On Fri, Sep 02, 2005 at 01:24:31PM +0200, Peter Veentjer - Anchor Men wrote:
> I have created a remote repository (ftp) and if I deploy jars it, it 
> works like expected. But if I build another project that depends on 
> something in my remote repository (and it jars/poms are there) I get 
> an error that the jars can`t be resolved. I have the feeling that I 
> only can write to the repository, but can`t read from it.
I think maven.repo.remote and maven.repo.mylokalreponame are different things. 
maven.repo.remot ist just for downloading and the other for uploading. So you 
should try maven.repo.remote=ftp://ftphost/java/repository

But I experienced that only http repos work for maven.repo.remote adn I had to 
set up a webserver for this.

Greetings,
  lothar




>  
> If I copy the jars/poms to my local repository, it works like it should.
>  
> This is a my build.properties (that is in my home directory)
> --
> --
> 
> #lijst van alle remote repositories
> maven.repo.remote=anchormen,http://www.ibiblio.org/maven
>  
> #lijst van repositories waarheen gedeployed moet worden 
> maven.repo.list=anchormen
>  
> #eigenschappen van de anchormen repository
> maven.repo.anchormen=ftp://192.168.1.194:21
> maven.repo.anchormen.directory=java/repository
> maven.repo.anchormen.username=maven
> maven.repo.anchormen.password=maven
>  
> What am I doing wrong?
>  
> 
> Met vriendelijke groet,
> 
> Peter Veentjer
> Anchor Men Interactive Solutions - duidelijk in zakelijke 
> internetoplossingen
> 
> Praediniussingel 41
> 9711 AE Groningen
> 
> T: 050-3115222
> F: 050-5891696
> E: [EMAIL PROTECTED]
> I : www.anchormen.nl http://www.anchormen.nl/>
> 
>  

--
Lothar Märkle - [EMAIL PROTECTED] Netpioneer GmbH - Beiertheimer Allee 18a - 
D-76137 Karlsruhe
Tel: 0721 / 9 20 60 43
Fax: 0721 / 9 20 60 30

-
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: no reads from my own remote, but writes go ok.

[Lothar Märkle]

On Fri, Sep 02, 2005 at 01:24:31PM +0200, Peter Veentjer - Anchor Men wrote:
> I have created a remote repository (ftp) and if I deploy jars it, it
> works like expected. But if I build another project that depends on
> something in my remote repository (and it jars/poms are there) I get an
> error that the jars can`t be resolved. I have the feeling that I only
> can write to the repository, but can`t read from it.
I think maven.repo.remote and maven.repo.mylokalreponame are different
things. maven.repo.remot ist just for downloading and the other for
uploading. So you should try
maven.repo.remote=ftp://ftphost/java/repository

But I experienced that only http repos work for maven.repo.remote adn I
had to set up a webserver for this.

Greetings,
  lothar




>  
> If I copy the jars/poms to my local repository, it works like it should.
>  
> This is a my build.properties (that is in my home directory)
> 
> 
> #lijst van alle remote repositories
> maven.repo.remote=anchormen,http://www.ibiblio.org/maven
>  
> #lijst van repositories waarheen gedeployed moet worden
> maven.repo.list=anchormen 
>  
> #eigenschappen van de anchormen repository
> maven.repo.anchormen=ftp://192.168.1.194:21
> maven.repo.anchormen.directory=java/repository
> maven.repo.anchormen.username=maven
> maven.repo.anchormen.password=maven
>  
> What am I doing wrong?
>  
> 
> Met vriendelijke groet,
> 
> Peter Veentjer
> Anchor Men Interactive Solutions - duidelijk in zakelijke
> internetoplossingen
> 
> Praediniussingel 41
> 9711 AE Groningen
> 
> T: 050-3115222
> F: 050-5891696
> E: [EMAIL PROTECTED]
> I : www.anchormen.nl http://www.anchormen.nl/> 
> 
>  

-- 
Lothar Märkle - [EMAIL PROTECTED]
Netpioneer GmbH - Beiertheimer Allee 18a - D-76137 Karlsruhe
Tel: 0721 / 9 20 60 43
Fax: 0721 / 9 20 60 30

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

no reads from my own remote, but writes go ok.

[Peter Veentjer - Anchor Men]

I have created a remote repository (ftp) and if I deploy jars it, it
works like expected. But if I build another project that depends on
something in my remote repository (and it jars/poms are there) I get an
error that the jars can`t be resolved. I have the feeling that I only
can write to the repository, but can`t read from it.
 
If I copy the jars/poms to my local repository, it works like it should.
 
This is a my build.properties (that is in my home directory)


#lijst van alle remote repositories
maven.repo.remote=anchormen,http://www.ibiblio.org/maven
 
#lijst van repositories waarheen gedeployed moet worden
maven.repo.list=anchormen 
 
#eigenschappen van de anchormen repository
maven.repo.anchormen=ftp://192.168.1.194:21
maven.repo.anchormen.directory=java/repository
maven.repo.anchormen.username=maven
maven.repo.anchormen.password=maven
 
What am I doing wrong?
 

Met vriendelijke groet,

Peter Veentjer
Anchor Men Interactive Solutions - duidelijk in zakelijke
internetoplossingen

Praediniussingel 41
9711 AE Groningen

T: 050-3115222
F: 050-5891696
E: [EMAIL PROTECTED]
I : www.anchormen.nl http://www.anchormen.nl/> 

 

Re: Best practices for release and version management?

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> Hi there,
> 
> How do you use to manage your project version among releases? I
> mean... what do you exactly put in currentVersion in your pom and how
> do you change it among releases?
> 
> I'm currently using the following approach:
> 
> 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT
> 2. V0.1 release: commit all pending changes, change currentVersion to
> 0.1, commit pom, tag/branch repository, make release.
> 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT,
> commit pom, update and continue developing

This is the way that we're recomending and using ourselfs.

> What do you think about this? This approach has one annoying thing:
> maven tries to download SNAPSHOT versions from remote repositories,
> although they're only locally installed in the developer repository.
> After some timeout maven uses the local version, but in case of large
> projects the sum of the timeouts may be big. Do you use any other
> approach?

The easiest solution to this problem is to either configure a proxy so it
doesn't time out (but rather get a 404 response from the HTTP server) or
just run Maven in off-line mode (by using the -o switch)

--
Trygve


signature.asc
Description: Digital signature

Re: Best practices for release and version management?

[Jose Gonzalez Gomez]

2005/9/2, Jose Gonzalez Gomez <[EMAIL PROTECTED]>:
> Hi there,
> 
> How do you use to manage your project version among releases? I
> mean... what do you exactly put in currentVersion in your pom and how
> do you change it among releases?
> 
> I'm currently using the following approach:
> 
> 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT
> 2. V0.1 release: commit all pending changes, change currentVersion to
> 0.1, commit pom, tag/branch repository, make release.
> 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT,
> commit pom, update and continue developing
> 
> What do you think about this? This approach has one annoying thing:
> maven tries to download SNAPSHOT versions from remote repositories,
> although they're only locally installed in the developer repository.
> After some timeout maven uses the local version, but in case of large
> projects the sum of the timeouts may be big. Do you use any other
> approach?
> 
> Thanks in advance, best regards
> Jose
> 

After re-reading some of the maven documentation it seems I'm
following the suggested approach (although manually, instead of using
the scm plugin)... anyway, is there any way to force maven to use the
local repository version of my own SNAPSHOT artifacts while still
downloading external dependencies?

Thanks in advance, best regards
Jose

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

Best practices for release and version management?

[Jose Gonzalez Gomez]

Hi there,

How do you use to manage your project version among releases? I
mean... what do you exactly put in currentVersion in your pom and how
do you change it among releases?

I'm currently using the following approach:

1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT
2. V0.1 release: commit all pending changes, change currentVersion to
0.1, commit pom, tag/branch repository, make release.
3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT,
commit pom, update and continue developing

What do you think about this? This approach has one annoying thing:
maven tries to download SNAPSHOT versions from remote repositories,
although they're only locally installed in the developer repository.
After some timeout maven uses the local version, but in case of large
projects the sum of the timeouts may be big. Do you use any other
approach?

Thanks in advance, best regards
Jose

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

Re: [M2] Problems with m2 site:site

[Yann Le Du]

Indeed, http://jira.codehaus.org/browse/MNG-476, then
http://jira.codehaus.org/browse/WAGONSSH-5

Though, there seems to be no fix planned for next release.

Thanks Jesse for the  trick, it's less harmful than patching the
source :)


Yann



--- Jesse McConnell <[EMAIL PROTECTED]> a écrit :

> there is a known bug in on that issue
> 
> 
> 
> 
> 
> 
> 
> org.apache.maven.plugins
> maven-site-plugin
> 
> /usr/bin/unzip -o > err.txt
> 
> 
> 
> 
> 
> 
> 
> there is some problem witht he unzip, if you do this then it ought to work 
> :)
> On 9/1/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
> > 
> > I get exactly the same error when I run site:site and I'm running on
> > the Mac OS X platform, and it seemed including a site.xml file didn't
> > cause any extra content to be generated.
> > 
> > Also the site:deploy goal fails for me. It did manage to zip up the
> > site directory, as I stopped it at the correct moment and examined
> > the contents. However it appears that the scp stage failed, as I
> > ended up with a zip file on the server that unzipped to no contents.
> > 
> > I notice there is an unusual -t switch on the scp - anybody know what
> > that's for?
> > 
> > 
> > On 1 Sep 2005, at 19:39, Jesse McConnell wrote:
> > 
> > > do you have
> > >
> > > 
> > > 
> > > site
> > > Gallup Plugins
> > > scp://host/devel/websites/site
> > > 
> > > 
> > >
> > > specified in a pom and the corresponding info in a setting.xml in
> > > your .m2
> > > directory?
> > >
> > >
> > > On 9/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > >>
> > >> Hi All,
> > >>
> > >> I'm trying to generate a site from an installed/deployable
> > >> application,
> > >> and receive the following:
> > >>
> > >> [INFO]
> > >> -
> > >> ---
> > >> [INFO] Building Maven Quick Start Archetype
> > >> [INFO]
> > >> -
> > >> ---
> > >> [INFO] maven-site-plugin: resolved to version 2.0-alpha-2 from local
> > >> repository
> > >> [INFO] Setting property: classpath.resource.loader.class => '
> > >> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> > >> [INFO] Setting property: resource.loader => 'classpath'.
> > >> [INFO] **
> > >> [INFO] Starting Jakarta Velocity v1.4
> > >> [INFO] RuntimeInstance initializing.
> > >> [INFO] Default Properties File:
> > >> org\apache\velocity\runtime\defaults\velocity.properties
> > >> [INFO] Default ResourceManager initializing. (class
> > >> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> > >> [INFO] Resource Loader Instantiated:
> > >> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> > >> [INFO] ClasspathResourceLoader : initialization starting.
> > >> [INFO] ClasspathResourceLoader : initialization complete.
> > >> [INFO] ResourceCache : initialized. (class
> > >> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> > >> [INFO] Default ResourceManager initialization complete.
> > >> [INFO] Loaded System Directive:
> > >> org.apache.velocity.runtime.directive.Literal
> > >> [INFO] Loaded System Directive:
> > >> org.apache.velocity.runtime.directive.Macro
> > >> [INFO] Loaded System Directive:
> > >> org.apache.velocity.runtime.directive.Parse
> > >> [INFO] Loaded System Directive:
> > >> org.apache.velocity.runtime.directive.Include
> > >> [INFO] Loaded System Directive:
> > >> org.apache.velocity.runtime.directive.Foreach
> > >> [INFO] Created: 20 parsers.
> > >> [INFO] Velocimacro : initialization starting.
> > >> [INFO] Velocimacro : adding VMs from VM library template :
> > >> VM_global_library.vm
> > >> [ERROR] ResourceManager : unable to find resource
> > >> 'VM_global_library.vm'
> > >> in any resource loader.
> > >> [INFO] Velocimacro : error using VM library template
> > >> VM_global_library.vm
> > >> : org.apache.velocity.exception.ResourceNotFoundException: Unable
> > >> to find
> > >> resource 'VM_global_library.vm'
> > >> [INFO] Velocimacro : VM library template macro registration complete.
> > >> [INFO] Velocimacro : allowInline = true : VMs can be defined
> > >> inline in
> > >> templates
> > >> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined
> > >> inline
> > >> may NOT replace previous VM definitions
> > >> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline
> > >> will be
> > >> global in scope if allowed.
> > >> [INFO] Velocimacro : messages on : VM system will output logging
> > >> messages
> > >> [INFO] Velocimacro : autoload off : VM system will not automatically
> > >> reload global library macros
> > >> [INFO] Velocimacro : initialization complete.
> > >> [INFO] Velocity successfully started.
> > >> [INFO] [site:site]
> > >> [INFO]
> > >> -
> > >> ---
> > >> [INFO] BUILD SUCCESSFUL
> > >> [INFO]
> > >> 

Re: Ibiblio javax.XYZ jars

[Trygve Laugstøl]

On Fri, Sep 02, 2005 at 08:03:03AM +0100, Matthew Smalley wrote:
> More of an Ibiblio question really. I want to build something which involves
> a transaction manager, Spring and Hibernate. In order to do that, I need
> interfaces from javax.transaction (typically referred to as jta). I've seen
> that http://www.ibiblio.org/maven/javax.transaction/ has a POM, and
> http://www.ibiblio.org/maven/javax.transaction/ has both a POM and a
> license, but I can't fathom out how with Maven 1 I can download the jar.
> 
> I guess this applies to not just jta, but a lot of the other javax.*
> packages (minus, surprisingly, servlet 2.4!).
> 
> Have I got this completely wrong?

We're not allowed to redistribute those JAR files because of Sun's
license. For your reference you can read [1].


> (PS to fix this, I've checked in my own version of jta (sound somewhere
> else), referenced with a jar override).

That's the way you have to do it.

[1]: http://maven.apache.org/reference/standard-sun-jar-names.html

--
Trygve


signature.asc
Description: Digital signature

Ibiblio javax.XYZ jars

[Matthew Smalley]

More of an Ibiblio question really. I want to build something which involves
a transaction manager, Spring and Hibernate. In order to do that, I need
interfaces from javax.transaction (typically referred to as jta). I've seen
that http://www.ibiblio.org/maven/javax.transaction/ has a POM, and
http://www.ibiblio.org/maven/javax.transaction/ has both a POM and a
license, but I can't fathom out how with Maven 1 I can download the jar.

I guess this applies to not just jta, but a lot of the other javax.*
packages (minus, surprisingly, servlet 2.4!).

Have I got this completely wrong?

(PS to fix this, I've checked in my own version of jta (sound somewhere
else), referenced with a jar override).

Matthew.