Hy,
I try to build the project from the root maven project but I faced some
compilation problems :
in maven-plugin-tools-javadoc
-
The profile toobtain tools.jar is not activate (so so xdoc and build failed),
this profile is activated by property java.vendor :
2012/6/27 Benson Margulies :
> Does @component inside the javadoc map to the @Component here?
yup :-)
>
> It it necessary to also have an @Parameter for read-only and required
> with an @Component?
A field can be a parameter or a component.
Maybe I miss you, you want to add both annotations to the
Does @component inside the javadoc map to the @Component here?
It it necessary to also have an @Parameter for read-only and required
with an @Component?
On Wed, Jun 27, 2012 at 3:31 PM, Olivier Lamy wrote:
> 2012/6/27 Marc Pasteur :
>> Hi
>> https://cwiki.apache.org/confluence/display/MAVEN/Jav
2012/6/27 Marc Pasteur :
> Hi
> https://cwiki.apache.org/confluence/display/MAVEN/Java+5+Annotations+for+Plugins?
Yup.
We used names very similar with doclet.
You can have a look here
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
>
> Regards,
> Marc
> Le 2
Hi
https://cwiki.apache.org/confluence/display/MAVEN/Java+5+Annotations+for+Plugins?
Regards,
Marc
Le 27 juin 2012 20:45, "Benson Margulies" a écrit :
>
> Could someone point me at a tutorial for this? We're changing shade to
> depend on M3, so we might as well move it to this.
>
> --
The truth of the matter is that the only way to get a reliable
timeline is if you make the fix yourself and give us a patch.
Codehaus JIRA is not currently available, so I can't check to see if
there's a complete test case attached to the JIRA, which would improve
the likelihood that one of us chi
Hi,
I would like to bring attention to http://jira.codehaus.org/browse/MSHADE-120.
Its a bug regarding the createSourceJar not including source from the current
maven module.
Do you guys have any timeline on when will this be fixed and release? Hopefully
soon!
Thank you,
Saurabh Ajmera
--
On Tue, 26 Jun 2012 09:03:36 +0200
Olivier Lamy wrote:
> Just applied.
> Thanks !
And now could we start a vote ?
I'd like to release license-m-p but there is a blocker issue (MPLUGIN-213) that
can not permit me to release the project.
thanks,
tony
--
+1 (binding)
On Wed, Jun 27, 2012 at 7:53 AM, Benson Margulies wrote:
> Hi,
>
> We solved 1 issues:
>
> ** Bug
> * [MSHADE-123] - 1.7 Causes failures in other plugins make
> "basedir" point to the build dir
>
>
> There are still plenty of issues left in JIRA.
>
> Staging repo:
> https://reposi
On Wed, Jun 27, 2012 at 7:39 AM, Olivier Lamy wrote:
> +1
> fine for me
OK, 1.7.1 staged and out for vote.
>
> 2012/6/27 Benson Margulies :
>> Here's my proposed plan.
>>
>> 1) I do something about MSHADE-123: move the default back to basedir.
>>
>> 2) I release 1.7.1.
>>
>> 3) You move the next
Hi,
We solved 1 issues:
** Bug
* [MSHADE-123] - 1.7 Causes failures in other plugins make
"basedir" point to the build dir
There are still plenty of issues left in JIRA.
Staging repo:
https://repository.apache.org/content/repositories/maven-282/
https://repository.apache.org/content/reposi
GitHub user anistor opened a pull request:
https://github.com/apache/maven-surefire/pull/5
SUREFIRE-879 maven-surefire-report-plugin fails some times with Concurre...
...ntModificationException when running parallel TestNG
The issue is easily fixed by atomically copying the
+1
fine for me
2012/6/27 Benson Margulies :
> Here's my proposed plan.
>
> 1) I do something about MSHADE-123: move the default back to basedir.
>
> 2) I release 1.7.1.
>
> 3) You move the next version to 2.0 or 3.0, and fix MSHADE-112.
>
> 4) I apply the patch to MSHADE-103 that requires us to de
On Wed, Jun 27, 2012 at 2:42 AM, Jörg Schaible
wrote:
> Benson Margulies wrote:
>
>> Folks,
>>
>> I've dug a hole (reported by) MSHADE-123 and I don't know what to do about
>> this.
>>
>> I dug the hole via the changes to move the default location of the
>> dependency reduced pom from the project
14 matches
Mail list logo
