You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ashley Williams <ag...@mac.com> on 2005/09/02 18:17:02 UTC

Re: [m2] eclipse plugin broken in a different way

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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] eclipse plugin breakage summary

Posted by Ashley Williams <ag...@mac.com>.
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
>>
>> <sourceDirectory></sourceDirectory> - 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.
>
>
>> <sourceDirectory>.</sourceDirectory> - 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.
>
>
>> <sourceDirectory>/</sourceDirectory> - 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.
>
>
>> <sourceDirectory>\\</sourceDirectory> - 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-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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] eclipse plugin breakage summary

Posted by Kenney Westerhof <fo...@neonics.com>.
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
>
> <sourceDirectory></sourceDirectory> - 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.

> <sourceDirectory>.</sourceDirectory> - 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.

> <sourceDirectory>/</sourceDirectory> - 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.

> <sourceDirectory>\\</sourceDirectory> - 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-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: users-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] eclipse plugin breakage summary

Posted by Ashley Williams <ag...@mac.com>.
Ok I get four different types of behaviour in eclipse depending on  
what text I put in sourceDirectory after running eclipse:eclipse

<sourceDirectory></sourceDirectory> - StringIndexOutOfBoundsException  
running eclipse:eclipse
<sourceDirectory>.</sourceDirectory> - sources in default package,  
dependency libs are ther
<sourceDirectory>/</sourceDirectory> - no package, no dependcy libs,  
java files directly under project root icon
<sourceDirectory>\\</sourceDirectory> - 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] eclipse plugin broken (sorry,still in the same way)

Posted by Ashley Williams <ag...@mac.com>.
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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org