Sorry, link missing -
http://sourceforge.net/projects/mvn-anno-mojo
--
View this message in context:
http://www.nabble.com/Plugin+descriptor+extractor+for+JDK1.5+sources-annotations--t1420471.html#a4475521
Sent from the Maven - Dev forum at Nabble.com.
-
I have already implemented the above, with APT and QDox-1.6-SNAPSHOT (which
lives peacefully with 1.5 syntax).
It is currently avalibale through SVN only.
I'll be glad to contribute this to Maven.
Yoav
--
View this message in context:
http://www.nabble.com/Plugin+descriptor+extractor+for+JDK1.
Thanks - just let us know if we can be of any help.
- Brett
Francis Long wrote:
> Hi Brett,
>
> One of our partner has developed this integration and we are talking with
> them for devoting this code.
>
>
> Thanks and best regards,
>
>
>
> Francis Long Guangyu
>
> Serena Software
>
>
John C put some requirements into the docck plugin, so determining what
they are and writing them out would be a good start. My thoughts:
* must have appropriate license files (LICENSE.txt, NOTICE.txt, POM element)
* must have a comprehensive reference of each option available in a plugin
* must
Ok, it should probably be a new issue in future. Thanks for the details.
- Brett
Maria Odea Ching wrote:
When it was previously closed, the excludePackageNames already accepts
wild cards.
Sample structure:
+--org.apache.maven
+--sample
+--subpackageToBeExcluded
--ClassTha
What is required on the codehaus server? Were there plexus changes?
Emmanuel Venisse wrote:
The merge is already done since Tuesday.
I'm not sure all works. I'll check it when codehaus server will be back.
Emmanuel
Brett Porter a écrit :
Hi,
I was wondering when the trunk merge was going to
[EMAIL PROTECTED] wrote:
/**
+ * Description passed to a generated POM file (in case of generatePom=true)
+ *
+ * @parameter expression="${generatePom.description}"
+ */
+private String description = "POM was created from deploy:deploy-file";
Wouldn't ${description} be
There are a number of JIRA issues related to velocity verbosity. All of
them are marked as fixed and yet the latest site plugin is spewing the
same drek as it has been for the last 6 months. Does something need to
be toggled or did the fix just not make it downstream into the site
plugin?
--
Hello
Checkstyle plugin site checkstyle mojo has no content:
http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html
I tried to generate it myself from sources.
It fails with an error during xml parsing for trunk and
tags/maven-checkstyle-plugin-2.1
Invalid xml fragment:
Hello
I am on working on a big project which is divided into 3 subprojects and
these subprojects are again divided into projects.
We were working with Maven 1 but we changed everything to use Maven 2 now.
With Maven 1, we managed with some Ant scripts and defined goals to
aggregate the repo
John, as you note there's no definitive answer. I've stressed the need
for usecase-based documentation which walks the user through the steps
required to do X, Y and Z. The clover plugin does a good job of this in
its howto.apt.
-Original Message-
From: John Tolentino [mailto:[EMAIL PRO
Roald Bankras wrote:
So for now, all I need to do is attach the diff file to the jira issue. Right?
Yep, and in time (hopefully short time) someone will take a look at it
and if it's good enough commit it.
--
Trygve
-
To un
It might be due the the harddisk failure at codehaus, but I'm not able the
resolve the issue. The file is attached, so for me its done. Thx for the help!
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, May 19, 2
I have to respecify my issueTracking details in module POMs that have a
dedicated JIRA project.
- Original Message -
From: "Mike Perham" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Thursday, May 18, 2006 11:19 PM
Subject: RE: New Issue Tracking URL for the recently released
So for now, all I need to do is attach the diff file to the jira issue. Right?
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, May 19, 2006 1:33 PM
To: Maven Developers List
Subject: Re: maven plugin development
Roald Bankras wrote:
I'm not allowed to resolve the task in jira. Can you do it for me?
It's MNG-2306.
You should be able to resolve it as the submitter, but it should not be
closed until it's commited in subversion and verified.
Furthermore, I'm not allowed to commit to subversion.
That'
I'm not allowed to resolve the task in jira. Can you do it for me?
It's MNG-2306.
Furthermore, I'm not allowed to commit to subversion.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, May 19, 2006 12:46 PM
To: Ma
Mike,
In regards to the javadoc aggregation report, I liked the idea of generating
scoped javadoc aggregtaion reports as i drilled into the project hierarchy
but noticed this wasnt possible, only the top-level project of reactor env
would generate the aggregation report.
If this 'only perfor
On 19 May 2006 at 11:30, Grzegorz Slowikowski wrote:
> Yes, you can.
>
> Greg
There is the BUG-ID: http://jira.codehaus.org/browse/MNG-2308
regards, carsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
Hi Brett,
One of our partner has developed this integration and we are talking with them
for devoting this code.
Thanks and best regards,
Francis Long Guangyu
Serena Software
TEL: +86 21 51160595
FAX: +86 21 51160780
Mobile: +86 139 1818 4826
www.serena.com
-Original Messa
Roald Bankras wrote:
Where is the maven site jira project? Or is there some otherway to comment the
commit?
The site uses the main JIRA project [1] and it has a set of 'components'
in that project.
Thanks for your work! :)
--
Trygve
When it was previously closed, the excludePackageNames already accepts
wild cards.
Sample structure:
+--org.apache.maven
+--sample
+--subpackageToBeExcluded
--ClassThatShouldNotBeExcluded.java
+--sample2
pom.xml plugin configuration:
*.sample2:org.apache.maven.samp
Where is the maven site jira project? Or is there some otherway to comment the
commit?
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, May 19, 2006 8:56 AM
To: Maven Developers List
Subject: Re: maven plugin dev
Yes, you can.
Greg
- Original Message -
From: "Carsten Karkola" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Friday, May 19, 2006 10:24 AM
Subject: Re: Maven 2.0.4 - Cascading POMs with packaging=pom
Hello,
thank you for verifying!
Can I create an JIRA issue or who is resp
Can't you just bind the plugin to a lifecycle phase in your pom?:
org.apache.maven.plugins
maven-assembly-plugin
package
jar-with-dependencies
assembly
Hope this helps
-Tim
Carsten Karkola schrieb:
Hel
Hello,
the usage of the assembly plugin is only possible via
mvn assembly:assembly
Is there a possibility to define something like
assembly
So I could do a
mvn package
in my multi-project directory and would get the needed assemblies without
special calls of some subprojects, where the ass
Hello,
thank you for verifying!
Can I create an JIRA issue or who is responsible for this?
regards, carsten
> >
> Hello
>
> Maven should look for parent pom in parent directory first.
> This have been described some time ago by Brett (I think).
>
> I have just tested it. It's a regression in Mav
Hi,
We're creating APT docs for the plugins. Currently there are no
standards on the format and content of a maven plugin site
documentation. Anybody have suggestions?
Regards,
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Why was this closed with a fix for in the past?
Maria Odea Ching (JIRA) wrote:
[ http://jira.codehaus.org/browse/MJAVADOC-56?page=all ]
Maria Odea Ching closed MJAVADOC-56:
Resolution: Fixed
excludePackageNames should accept wildars
---
Hi Kevin,
I was wondering if there had been any further progress on this matter?
Thanks,
Brett
Kevin Parker wrote:
Dear Maven’s,
We have recently developed a Maven interface for our PVCS product and
are interested in the process for potentially donating this to the
project. Could someone co
30 matches
Mail list logo