+1
Its in my settings.xml too.
On 7/3/07, Mark Hobson [EMAIL PROTECTED] wrote:
Following the recent thread Maven POM plugin config, this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy
Ooopps! I sent the other one to the user list... :(
Here are the changes I've made:
- created three sample usages:
- attaching library sources
- preventing module references
- providing project natures and build commands
- added three FAQ entries
- some fixes to improve site
Sounds odd, bec both the eclipse and idea plugins are generating 10 of
the project reports in my machine. I even ran it on javadoc and found
the same 10 reports.
I do agree about the checkstyle plugin being placed inside the pom but
not configured... since its there, we might as well fix
Hi,
--- index.html
This, thus, allows the separation ...
should be
Thus, this allows the separation...
--- encoding.html
encodingUTF-8/aggregate
should be
encodingUTF-8/encoding
^_^
FA Valencia See wrote:
Good day,
I would like to ask for some help reviewing M2's
On 7/18/06, Edwin Punzalan [EMAIL PROTECTED] wrote:
Ooopps! I sent the other one to the user list... :(
Here are the changes I've made:
- created three sample usages:
- attaching library sources
- preventing module references
- providing project natures and build commands
- added three
Hi,
I've just created the staging site for this plugin:
http://people.apache.org/~epunzalan/maven-compiler-plugin/
and would appreciate your feedback/comments.
Thanks in advance.
^_^
-
To unsubscribe, e-mail: [EMAIL
Done, thanks.
Staging site updated.
Dennis Lundberg wrote:
Edwin Punzalan wrote:
Hi,
I've just created the staging site for this plugin:
http://people.apache.org/~epunzalan/maven-compiler-plugin/
and would appreciate your feedback/comments.
Thanks in advance.
Here's my review
Updates applied. Staging site, updated.
Thanks.
^_^
Dennis Lundberg wrote:
Edwin Punzalan wrote:
Ooopps! I sent the other one to the user list... :(
Here are the changes I've made:
- created three sample usages:
- attaching library sources
- preventing module references
Allan,
Here are the things I found that may need improvement:
index.html
- Examples section, usecases should be use-cases.
usage.html
- All of the providers support the following configuration., where
are the configurations?
Allan Ramirez wrote:
Hi everyone,
Just updated the
Hi,
I've made some changes to the documentation of the Assembly plugin and
would like to hear your inputs about it.
- made the plugin docck-compliant
- edited the descriptions inside the modello files
- edited some of the parameter descriptions
- added an faq page
- added some single
Assembly Plugin on page headings
- added the Usage section in index.html
Again, thanks to the reviewers.
NOTE: The link to the javadoc plugin will fail bec the javadoc plugin
isn't in there. :P
^_^
Edwin Punzalan wrote:
Hi,
I've made some changes to the documentation of the Assembly plugin
Hi,
Thanks for the review. Please see my inline comments below...
Dennis Lundberg wrote:
Hi Edwin
I have committed a fix for a few typos.
Here are some additional comments om the assembly plugin documentation:
assembly-mojo.html
- archiverManager, artifactResolver and repositoryAssembler
I agree. Although its name is not bad, I think we can still think of a
better name than just plain Repository Manager.
Although I do not object to naming the list as
[EMAIL PROTECTED], I am also willing to wait for
better names that may come out.
Brett Porter wrote:
Hi,
I was
staging site updated with a patch from MASSEMBLY-130 applied.
Again, thanks for the reviewers. ^_^
Edwin Punzalan wrote:
Hi,
I've made some changes to the documentation of the Assembly plugin and
would like to hear your inputs about it.
- made the plugin docck-compliant
- edited
Hi,
I've made some changes to the documentation of the EAR plugin and would
like to hear your inputs about it.
- made the plugin docck-compliant
- separated the usage examples into separate example pages
- added an faq page
- added some single project examples
A staging site is currently
Hi,
Here are my comments:
* usage.html
- replace the word m2 with Maven
- explain the default configuration values used (when running the
plugin without any configuration)
- A user would like to see a sample report generated by this plugin.
Can you provide one like what Allan did for the
/
/artifactTypeMappings
/configuration
http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch13.html
Otherwise, this is really really good!!
Thanks,
Stéphane
On 7/31/06, Edwin Punzalan [EMAIL PROTECTED] wrote:
Hi,
I've made some changes to the documentation of the EAR plugin and would
like
Staging site updated with the following modifications:
- modules should start with lower case letters
- proper way of handling faq entry #2
- added mini-guide for the solution to faq entry #2
- fixed copy/paste errors in modules configuration page
Edwin Punzalan wrote:
Hi,
I've made some
+1 for Curator
^_^
nhb wrote:
Hi,
Brett invited me to post an idea or two I had to the list:
Maven Curator
# The person responsible for developing and maintaining collections.
http://www.lib.unc.edu/instruct/manuscripts/glossary/
# A person who catalogs and cares for artifacts after
If IDEA is correct, it can be declared final bec it didn't find any
other classes setting its value. Also, the naming would suggest that
author meant it to be final.
The tests also passed if after I changed it to final.
So I'd declare them as final.
Franz Allan Valencia See wrote:
Good
With regards to this, I tried fixing the Maven Assembly Plugin test
failures... but I need a SNAPSHOT of file-management in maven-shared
which is not deployed yet.
I then deployed a snapshot of maven-shared-io which is required to build
the file-management project.
Then I get to build the
I'll look into some of them...
^_^
Brett Porter wrote:
Does anyone have time to apply an occasional patch?
I keep track of them and I now count 223 outstanding. I know many are
sometimes a bit off base, but there's two problems with this:
- we have potential fixes for issues already
- we
Hi,
my bad. I'll revert asap.
I had my settings.xml configured for snapshots repositories, both for
codehaus and apache. Apparently when I tried building this plugin,
maven didn't find any 2.0.5-SNAPSHOT so I thought the dep was wrong and
changed it to 2.1-SNAPSHOT since the trunk is
expressed a preference for a single one other than
proposing it): Brian Fox, Allan Ramirez, Maria Odea Ching, Edwin
Punzalan, Brett Porter, Wendell Beckwith
We will create mailing lists:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Then, SVN will be renamed and I'll put together a beta
at the bottom?
Cheers,
Brett
On 29/08/2006, at 2:07 PM, Edwin Punzalan wrote:
Hi,
After consulting with Brett, we've come up with the white site for
releasing projects using continuum. Brett, if I missed something,
please do remind me.
I've deployed here for your viewing:
http
I'll fix this asap. Thanks.
Brett Porter wrote:
On 08/09/2006, at 8:50 PM, [EMAIL PROTECTED] wrote:
Author: epunzalan
Date: Fri Sep 8 03:50:09 2006
New Revision: 441469
URL: http://svn.apache.org/viewvc?view=revrev=441469
Log:
PR: CONTINUUM-727
+private final int phaseSkip = 0,
CONTINUUM-970 has been created for this... you can apply the patch there
in your local copy if you want.
Hope that helps.
^_^
Martin van den Bemt wrote:
Hi everyone,
Building continuum is kind of a pain and is not working out for me.
The problem may be due to the apache snapshot repo
Did that failure just return? I tried building it and I didn't get the
failure. I remember evenisse fixed something like this.
Again, was probably caused by the outdated snapshot repo, this time for
the maven-scm. Installing maven-scm locally should do the trick.
And again, someone should
This is good. Great work.
^_^
Eric Redmond wrote:
Interesting. I'll do it.
On 10/29/06, Brett Porter [EMAIL PROTECTED] wrote:
Anyone interested in this?
Begin forwarded message:
From: Will Lin [EMAIL PROTECTED]
Date: 26 October 2006 2:10:53 PM
To: [EMAIL PROTECTED] [EMAIL
release manager can be found here:
http://svn.apache.org/repos/asf/maven/shared/trunk/maven-release-manager
Barrie Treloar wrote:
Can any snapshot releases also have the source attached as part of the
deployment?
There is an error filed at
http://jira.codehaus.org/browse/CONTINUUM-968 which
The trunk for maven-release-manager fails bec somehow, the exception
thrown has been changed in the latest snapshot of maven-scm.
I'll fix the failure in a while.
Barrie Treloar wrote:
Can any snapshot releases also have the source attached as part of the
deployment?
There is an error
Trunk is now fixed in svn.
Edwin Punzalan wrote:
The trunk for maven-release-manager fails bec somehow, the exception
thrown has been changed in the latest snapshot of maven-scm.
I'll fix the failure in a while.
Barrie Treloar wrote:
Can any snapshot releases also have the source
+1
^_^
Joakim Erdfelt wrote:
Hi,
It has been 5 months since the last release of the maven-checkstyle-plugin,
Since then, there have been numerous fixes to correct various site
generation failures, updated maven ruleset, some cleanup of the report
layout, header refactoring, revised
hmm... didn't know such a plugin exists is it in codehaus ?
Jason van Zyl wrote:
Just curious but any reason why this is not in a Selenium plugin?
Jason.
On 10 Nov 06, at 7:29 PM 10 Nov 06, [EMAIL PROTECTED] wrote:
Author: epunzalan
Date: Fri Nov 10 16:29:18 2006
New Revision: 473592
Fix version is 2.0.5... so you'll have to wait for the next release or
use the latest snapshot to use the fixed version
David Whitehurst wrote:
Is this still an issue? I don't understand the comments.
http://jira.codehaus.org/browse/MNG-2261;jsessionid=atZK5r5j2N8bRm0-m5
I want to use an
+1
John Tolentino wrote:
Hi Everyone,
The latest version (2.0.2-SNAPSHOT) of the maven-war-plugin is now
deployed to the snapshot repo. We'll also have the license stuff
resolved before doing any release.
For your reference of features included in this release:
oh, yeah. Sorry about that, wasn't intentional... i'll edit my comment
in there, thanks
Brett Porter wrote:
Edwin,
You should list who submitted the fix in the comment.
- Brett
On 11/12/2006, at 7:30 PM, [EMAIL PROTECTED] wrote:
Author: epunzalan
Date: Mon Dec 11 00:30:32 2006
New
I'm not sure if eclipse supports it, but with IDEA, the package view
keep the resources and the java sources together.
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there everybody,
from the separation of concerns view of the maven plugins I can see the point in
you can set it in cli,
-Dappserver.base=C:\EclipsePack\continuum\trunk\continuum-webapp\target
^_^
Christophe LECHENNE wrote:
Hi all,
After a successful build, when I try to start continuum as it's written in README.txt, I've got :
java.io.FileNotFoundException:
try here: http://svn.apache.org/repos/asf/maven/surefire/trunk
^_^
TslH wrote:
Hello,
I wanted to have a look to Surefire plugin, in order to see why TestNG
5.xdon't work with it. But when I browsing SVN, I can't find surefire
sources.
I'm trying to get them through:
/source-repository.html,
since it's awfully outdated.
Have a nice day.
2006/12/26, Edwin Punzalan [EMAIL PROTECTED]:
try here: http://svn.apache.org/repos/asf/maven/surefire/trunk
^_^
TslH wrote:
Hello,
I wanted to have a look to Surefire plugin, in order to see why TestNG
5.xdon't work
that's ok.
Merry christmas!
^_^
TslH wrote:
Awfully was not the right word, I apologize. Another trick played by my
bad english ;)
2006/12/26, Edwin Punzalan [EMAIL PROTECTED]:
The site was last published Nov 7... and the source repository was moved
Dec 20.
Its just a bit outdated
+1
Brett Porter wrote:
I'd like to propose we make Barrie a committer. He has contributed a
lot of small patches, and recently seems to be the does it work on
Windows? watchdog. He in particular has done a lot with the assembly
plugin and has also dug into some of the components in Plexus to
+1
Brett Porter wrote:
Hi,
Vote to operate as
- requiring 2/3rds of the PMC to vote (13), with a majority within
those votes for it to pass (ie, add them all and if the result is
0). Other votes would be welcome with reasons as advisory, but not
binding.
- Votes can be changed at any time
Brett,
Its failing in phase check-dependency-snapshot phase... the phase uses
project.getArtifacts() which is not populated when its missing
Brett Porter wrote:
Edwin - can we double check the requirement here. I recently removed
this to prevent the problem of it failing if you haven't
getArtifacts() be changed to getDependencies()
without changing the meaning? (Sorry, I haven't looked, I just know
the dep resolution was problematic)
- Brett
On 01/02/2007, at 2:54 PM, Edwin Punzalan wrote:
Brett,
Its failing in phase check-dependency-snapshot phase... the phase
uses
in the repository already, as it was working for me...
Can the code using getArtifacts() be changed to getDependencies()
without changing the meaning? (Sorry, I haven't looked, I just know
the dep resolution was problematic)
- Brett
On 01/02/2007, at 2:54 PM, Edwin Punzalan wrote:
Brett
Please see:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/plexus/security/plexus-security/1.0-alpha-8/plexus-security-1.0-alpha-8.pom
Its clear that the release manager failed to update the expression
definition of the dependency versions. Fixing this bug will be easy if
only
Hi,
I've seen that **/pom.xml is being ignored for local modifications
during a release... Although that doesn't seem right because when the
release is committed, the changes will become part of the release
process, I have found a use for it when dryRun=true... that is, to test
a release of
Kenney Westerhof wrote:
Edwin Punzalan wrote:
Hi,
I've seen that **/pom.xml is being ignored for local modifications
during a release... Although that doesn't seem right because when the
release is committed, the changes will become part of the release
process, I have found a use
Brett Porter wrote:
On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote:
AFAIK the reason the poms are excluded is because they're modified
by the
release process; if the check for local modifications is run after
the pom
is modified, it's impossible to do a release. So this could probably
What is it that you want the release-plugin to do? If you just want to
specify a different version than what is recommended by the plugin when
it prompts them, then it should be safe to do without any problems.
^_^
Guijie (Maggie) Ma wrote:
Hi,
I'm a user of Maven and Maven is very
If we want the release-plugin deal with this automatically,
what problem dose it have? Can the developers give us some suggestion or help?
Thank you!
Maggie Ma
Edwin Punzalan [EMAIL PROTECTED] 2/11/2007 4:21 AM
What is it that you want the release-plugin to do? If you just want
automatically?
I have attached the snapshot of the release-prepare.
Thanks!
Maggie
Edwin Punzalan [EMAIL PROTECTED] 2/11/2007 8:05 PM
I don't think there will be any problems if you put in the configuration
all the versions you will want to use. Continuum have a similar process
too
unfortunately, you can't. If in continuum, the user is prompted for all
the versions.
What the plugin does however is suggest a default, which is what it
currently does. Of course, the default isn't always appropriate for all
cases, but generally it should suffice.
If you want a new
well although this about Maven and modules *may* be true, the release
plugin can release the modules with a different versions than what is
declared in the parent. That's why the release plugin prompts for the
release/dev versions even though the project will inherit them. If you
specified
hahaha!
nice catch... I guess I'm depending too much with my IDE.
I'll do it, thanks.
^_^
Brett Porter wrote:
On 14/02/2007, at 4:49 PM, [EMAIL PROTECTED] wrote:
-ScmRepository repository = getScmRepositorty( project );
+ScmRepository repository =
I like this... good thing archiva have people like you ;)
^_^
Joakim Erdfelt wrote:
I hope to have this 'State of the Archiva' be a fairly regular report
here in the archiva-dev@maven.apache.org mailing list.
Here, the Past, Present, and Future of Archiva will be outlined.
:: PAST ::
That's odd. Mine doesn't build a project if there are no SCM changes.
The projects in my Continuum instance are from an SVN repo. Maybe its
an SCM-related problem. What's your SCM provider? Are you sure there
aren't any changes?
[EMAIL PROTECTED] wrote:
can I configure that a clean
Message-
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 6:42 AM
To: continuum-dev@maven.apache.org
Subject: Re: build loop feature 4 continuum?
That's odd. Mine doesn't build a project if there are no SCM changes.
The projects in my Continuum instance
org.apache.maven.continuum.buildcontroller.DefaultBuildController). so no
starteam provider problem here, thanx
-Original Message-
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 6:42 AM
To: continuum-dev@maven.apache.org
Subject: Re: build loop feature 4 continuum?
That's odd. Mine doesn't build
I've been looking at both proximity and maven-proxy features for reuse
with the MRM proxy. I would like to ask you guys what you think on
these features:
- browsable repositories
- maven-proxy browsability is on a per-repository browsing
- proximity browsability is a view of
Sorry...
I'll get those fixed soon... thanks.
^_^
Brett Porter wrote:
[EMAIL PROTECTED] wrote:
+public void testExceptions()
+ throws Exception
+{
+//test when the object passed in the index(..) method is not a
RepositoryMetadat instance
+
About the FLD_ID, the delete method for a document cannot have more than
one Term object for groupId, artifactId, and version so an ID is used.
i apologize about the others, I'll fix them right away...
Brett Porter wrote:
I think this is a possible NPE...
[EMAIL PROTECTED] wrote:
+
I think one of the commits after this fixed it. ^_^
Brett Porter wrote:
[EMAIL PROTECTED] wrote:
Modified: maven/repository-manager/trunk/maven-repository-utils/pom.xml
URL:
great! Patch applied... thanks.
Odea Ching wrote:
maven-repository-application.patch file:
- fix error in IndexSearcherCli
- changed ArtifactRepositoryIndexSearcher searcher =
indexFactory.createArtifactRepositoryIndexSearcher( index ) to
DefaultRepositoryIndexSearcher searcher =
sorry, just got to read this now... will change it now. Thanks.
Emmanuel Venisse wrote:
I think it will be better to use a logger instead of
System.out.println in DiscoverJob.
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: epunzalan
Date: Thu Mar 2 01:53:40 2006
New Revision: 382337
URL:
+1
^_^
Brett Porter wrote:
Hi,
Fabrice worked on the JXR plugin, fixed a number of bugs in the original
library and improved the mojo. Active on the users list, with a
particular interest in the site plugin, I believe would be a good
addition to the project.
Please vote:
[ ] +1
[ ] +0
+1
^_^
Brett Porter wrote:
Hi,
Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugin there, which we previously indicated
we'd like to have as a part of the Maven plugin artillery.
He has also actively helped on the users list and
+1
(what's non-binding?)
^_^
John Casey wrote:
Hi again,
I wanted to let everyone know that we've got the latest round of
regressions fixed, including:
* Fabrizio's lingering path problems from MNG-2006
* MNG-2136
* MNG-2124
* MNG-2130
These fixes also took care of some other
fyi, I've seen changelog and it already uses maven-scm
Brett Porter wrote:
I've been in favour of this since day 1. JXR, for example, is almost
entirely shared.
For changelog, this will happen by refactoring to Maven SCM. For
changes/jira/announcement, it will be by refactoring around
+1
^_^
Brett Porter wrote:
Hi,
John has been helping out on the users list, plugins and the repository
manager for some time. I'd like to propose we give him commit access.
[ ] +1
[ ] +0
[ ] -1
Cheers,
Brett
-
To
+1
^_^
Brett Porter wrote:
Hi,
Like John, Deng has been helping out on the users list, plugins and the
repository manager for some time. I'd like to propose we give her commit
access.
[ ] +1
[ ] +0
[ ] -1
Cheers,
Brett
+1
^_^
Brett Porter wrote:
Hi,
I think we all agree we need more keen people helping out with plugins!
Jesse has been contributing on the users list and mojo project for some
time, and has recently contributed several patches to the Apache Maven
plugins, tests for the clean, compiler and
hmmm... you're right.
Seems like assembly is excluding all META-INF/plexus/components.xml and
creating/adding the temp file for it even if the file is NOT in include
and/or is excluded. This IS a bug.
I'll create a jira issue for this
Brett Porter wrote:
META-INT?
[EMAIL PROTECTED]
when filtered is true, it means expressions like
${project.build.directory} inside the file is replaced with the actual
value when used in your pom.xml
dan tran wrote:
Hello, I am trying to fix
http://jira.codehaus.org/browse/MASSEMBLY-100 and
having trouble
understanding the purpose of
hi.
sorry, but i can't update my windows svn copy of this bec there's
already readme.apt.
[EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sun May 21 13:13:00 2006
New Revision: 408479
URL: http://svn.apache.org/viewvc?rev=408479view=rev
Log: (empty)
Added:
Fixed in svn. Thanks.
Grzegorz Słowikowski wrote:
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
${basedir} has backslashes... and is parsed wrongly by:
p.load( new StringInputStream( propertyExpansion ) );
Carsten Karkola wrote:
We have our own checkstyle config with some file references. I tried
to use them with
plugin
groupIdorg.apache.maven.plugins/groupId
Although not a real solution, but I have a workaround for some of the
use cases. Some parameters of the plugins similar to ${parameter} can
be configured inside settings.xml... just use properties.
^_^
Tomasz Pik wrote:
Hello,
It's currently not possible but generally I think it would
is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+/**
+ * @author Edwin Punzalan
+ */
+public interface Discoverer
Definitely deserves +1
However, I'm still torn between using apt and a wiki site but whichever
wins I think the obvious casualty will be the site-plugin.
If we continue on using the pages generated by the site plugin, and
based from John Casey's Core Documentation point #2, it will be a
Have you tried using the assembly plugin for this? The assembly plugin
can work on project sources and/or binaries.
Ovidio Mallo wrote:
Hi,
a few days ago I have posted a request on the Maven user list for some
way to create a source bundle for an artifact which not only includes
the
2.0-beta-2-SNAPSHOT can be found here:
http://snapshots.maven.codehaus.org/maven2/org/codehaus/mojo/changes-maven-plugin/
Jochen Wiedmann wrote:
Hi,
is there a snapshot of the maven-changes-plugin available somewhere? I would
like to do a release Apache XML-RPC, where I am using this
The url I gave have the snapshot timestamped on Jan 13...
The latest is already in apache and no snapshots have been deployed yet.
Jochen Wiedmann wrote:
Hi,
is there a snapshot of the maven-changes-plugin available somewhere? I would
like to do a release Apache XML-RPC, where I am using
do not have any work-around in mind for
your problem.
Ovidio Mallo wrote:
Edwin Punzalan wrote:
Have you tried using the assembly plugin for this? The assembly
plugin can work on project sources and/or binaries.
I have already looked at the assembly plugin as it would be the most
intuitive
Heheh, I didn't notice that... I just copied that from the other class. ^_^
btw, is that supposed to be 2006 only or 2001-2006 ? I remember Carlos
said I'd change only the latter part
Brett Porter wrote:
[EMAIL PROTECTED] wrote:
+ * Copyright 2001-2005 The Apache Software Foundation.
This issue was re-opened for the docs... and i've updated the docs so I
closed it.
Brett Porter wrote:
Was this actually fixed, or Cannot reproduce?
- Brett
On 19/06/2006 7:46 PM, Edwin Punzalan (JIRA) wrote:
[ http://jira.codehaus.org/browse/MSITE-149?page=all ]
Edwin Punzalan
May I add, based from the currently deployed site, the first page you
get after clicking the plugin name, is
Project Info - About
which is a replica of the page
Project Reports - Plugin documentation
just fyi
Pete Marvin King wrote:
I think it's a good idea to be able to pull
You can put any artifact as a dependency (whether it contains classes or
just plain text files doesn't matter ) and then you can get files from
it using the classloader Resource.
Marcin Maciukiewicz wrote:
Hello!
I'm working on Maven plugin for building project using 3rd party tools.
Regarding the scm tag, only warnings are produced from them, as what
brett stated in his doc standard email.
Brett Porter wrote:
On 27/06/2006 8:48 AM, Dennis Lundberg wrote:
Hi all
I've had a look at the docck plugin and I like what I see so far! A
couple of questions that popped up
There are classes inside maven-eclipse-plugin which are meant to be
extended/used by IDE plugins. Is it not worthwhile to extract it into a
separate artifact first, before working on another IDE plugin? After
that, the idea plugin should also be updated to use it.
Just my two cents. ^_^
+1
I see no generated pages showing these anywhere... ( or am I blind? ^_^ )
Jesse McConnell wrote:
could it show the class lvl phase and goal settings and perhaps if it
requiresDependencyResolution and that sort of thing?
nice improvement though :)
jesse
On 6/28/06, Brett Porter [EMAIL
+1 for moving the default value. A lot of the other comments want the
default value at the top of the page. Showing the default value in a
sentence is nice too.
It just somehow becomes complicated because expressions functions
somewhat like a default value, too. Any suggestions on how to
Should the page below suffice for a cheat sheet?
http://maven.apache.org/developers/mojo-api-specification.html
I think its too much info for a beginner since its meant for a plugin
developer... maybe someone here knows of a similar page meant for a user?
Mike Perham wrote:
For
Now that we're starting to *properly* document plugins and
prerequisites is now a required pom element, I think that it a default
should be placed in the plugin-parent pom.xml.
However, prerequisites is not an inherited pom element so I'd like to
ask if allowing prerequisites to be
There's a guide for configuring plugins and it mentions lists and maps...
http://maven.apache.org/guides/mini/guide-configuring-plugins.html
Brett Porter wrote:
On 29/06/2006 4:14 PM, Wendy Smoak wrote:
On 6/28/06, Brett Porter [EMAIL PROTECTED] wrote:
Sorry, but I don't really
May I add, that when maven already downloaded a poor/invalid pom, even
after fixing the pom in the repository, maven won't know that it's
changed (unless the version changed) and it will not download it. So
you end up still using your local repo copy.
To re-download a pom, you have to
Have you checked these out:
http://maven.apache.org/developers/mojo-api-specification.html
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
Russell, Mark wrote:
Actually I was thinking more of the list that a custom plugin could get.
IE If I'm writing a plugin, what's
except for the changelog plugin... its not in the parent bec I'd prefer
that the changelog should be configured such that it should show the
changes since the last release of the plugin.
Brett Porter wrote:
Hi Dennis,
These should be inherited from the parent if you set the parent to
1 - 100 of 519 matches
Mail list logo
