Re: [mojo-dev] JSPC plugin fixed

I think we better ensure the old one works again in 2.0.2. There is an
open issue.

- Brett

Jeff Genender wrote:
> I had reports about the jspc plugin not working in maven 2.0.1.  I
> upgraded to maven 2.0.1 and sure enough it broke the jspc plugin due to
> a change in the maven classloaders.  I fixed the plugin to make a
> URLClassloader and put it in the classloading chain and all works again.
>  So if you have encountered this problem, please update.
>
> Jeff
>
>   

Re: [mojo-dev] JSPC plugin fixed

Can you elaborate?  It would be nice to know if there will be more
classloader fun  coming down 

Brett Porter wrote:
> I think we better ensure the old one works again in 2.0.2. There is an
> open issue.
> 
> - Brett
> 
> Jeff Genender wrote:
>> I had reports about the jspc plugin not working in maven 2.0.1.  I
>> upgraded to maven 2.0.1 and sure enough it broke the jspc plugin due to
>> a change in the maven classloaders.  I fixed the plugin to make a
>> URLClassloader and put it in the classloading chain and all works again.
>>  So if you have encountered this problem, please update.
>>
>> Jeff
>>
>>   

Re: [mojo-dev] JSPC plugin fixed

If 2.0 -> 2.0.1 broke a plugin, then I expect we need to fix that.

There are a few issues with classloaders floating around WRT plugins.
We'll sort them all out in the core, hopefully.

- Brett

Jeff Genender wrote:
> Can you elaborate?  It would be nice to know if there will be more
> classloader fun  coming down 
>
> Brett Porter wrote:
>   
>> I think we better ensure the old one works again in 2.0.2. There is an
>> open issue.
>>
>> - Brett
>>
>> Jeff Genender wrote:
>>     
>>> I had reports about the jspc plugin not working in maven 2.0.1.  I
>>> upgraded to maven 2.0.1 and sure enough it broke the jspc plugin due to
>>> a change in the maven classloaders.  I fixed the plugin to make a
>>> URLClassloader and put it in the classloading chain and all works again.
>>>  So if you have encountered this problem, please update.
>>>
>>> Jeff
>>>
>>>   
>>>       

Re: [mojo-dev] Sites with incorrect permissions

I've fixed all the permissions. Go ahead and redeploy :)

- Brett

Brian E. Fox wrote:
> I tried to fix the non-sandbox sites as a lot of them have bad scm
> urls on the project pages. I ran into a couple of projects that can't
> be deployed because the group perms aren't set:
>  
> jxr
> jboss
> axistools
> taglist
> xmlbeans

Re: [mojo-dev] JSPC plugin fixed

No problem.  I suspect this change I made will likely be pretty solid
since before, I just assumed I was using Maven's URLClassloader.  Since
I now am creating my own URLClassloader and stuffing it with the
compile-time dependencies, I think it will stick.  In any case, it works
good now, and if I need to update yet again, it should not be a problem.
 But I suspect my injecting my own classloader will be a permafix.

Thanks for your response on this, Brett.

Jeff

Brett Porter wrote:
> If 2.0 -> 2.0.1 broke a plugin, then I expect we need to fix that.
> 
> There are a few issues with classloaders floating around WRT plugins.
> We'll sort them all out in the core, hopefully.
> 
> - Brett
> 
> Jeff Genender wrote:
>> Can you elaborate?  It would be nice to know if there will be more
>> classloader fun  coming down 
>>
>> Brett Porter wrote:
>>   
>>> I think we better ensure the old one works again in 2.0.2. There is an
>>> open issue.
>>>
>>> - Brett
>>>

RE: [mojo-dev] [vote] release dependency-maven-plugin 1.0

[mojo-dev] [jira] Created: (MOJO-201) surefire-report-maven-plugin: don't add report for non java projects

surefire-report-maven-plugin: don't add report for non java projects
--------------------------------------------------------------------

         Key: MOJO-201
         URL: http://jira.codehaus.org/browse/MOJO-201
     Project: Mojo
        Type: Bug

  Components: JUnit Report  
    Versions: 2.0-beta-1    
    Reporter: fabrizio giustina
     Fix For: 2.0
 Attachments: MOJO-surefirereport.diff

the surefire report should not be executed for non java (e.g. pom) projects.

+    /**
+     *  <at> see org.apache.maven.reporting.AbstractMavenReport#canGenerateReport()
+     */
+    public boolean canGenerateReport()
+    {
+        // Only execute reports for java projects
+        ArtifactHandler artifactHandler = this.project.getArtifact().getArtifactHandler();
+        return "java".equals( artifactHandler.getLanguage() );
+    }

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[mojo-dev] [jira] Closed: (MOJO-201) surefire-report-maven-plugin: don't add report for non java projects

     [ http://jira.codehaus.org/browse/MOJO-201?page=all ]

Carlos Sanchez closed MOJO-201:
-------------------------------

     Assign To: Carlos Sanchez
    Resolution: Fixed

> surefire-report-maven-plugin: don't add report for non java projects
> --------------------------------------------------------------------
>
>          Key: MOJO-201
>          URL: http://jira.codehaus.org/browse/MOJO-201
>      Project: Mojo
>         Type: Bug

>   Components: JUnit Report
>     Versions: 2.0-beta-1
>     Reporter: fabrizio giustina
>     Assignee: Carlos Sanchez
>      Fix For: 2.0
>  Attachments: MOJO-surefirereport.diff
>
>
> the surefire report should not be executed for non java (e.g. pom) projects.
> +    /**
> +     *  <at> see org.apache.maven.reporting.AbstractMavenReport#canGenerateReport()
> +     */
> +    public boolean canGenerateReport()
> +    {
> +        // Only execute reports for java projects
> +        ArtifactHandler artifactHandler = this.project.getArtifact().getArtifactHandler();
> +        return "java".equals( artifactHandler.getLanguage() );
> +    }

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[mojo-dev] Mojo synch to ibiblio missing hashes

RE: [mojo-dev] Mojo synch to ibiblio missing hashes