Re: Maven 1.x Model javadocs in Maven website
Thats right but it's normal ;-) Those classes are genarated and we generate them in 2 packages (org.apache.maven.model and org.apache.maven.project) to keep a backward compatibility with m1.0 Arnaud On 10/07/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: Just an FYI, the classes in the Maven 1.x Model javadocs (Maven website) are duplicated: http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/apidocs/index.html Thanks, Deng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 1.x Model javadocs in Maven website
Just an FYI, the classes in the Maven 1.x Model javadocs (Maven website) are duplicated: http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/apidocs/index.html Thanks, Deng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource filtering thoughts...
On Monday 09 July 2007 19:08, Kenney Westerhof wrote:
> Daniel Kulp wrote:
> > On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
> >> Daniel Kulp wrote:
> > Yep. That's the #1 issue.I've completely given up on trying to
> > get the string "${pom.version}" outputted into the file.
>
> Ok, but why are you filtering a file with that in there? Do you need
> filtering at all, or do you only want some things filtered?
>
> You can exclude specific files from filtering; doesn't that solve your
> problem?
It has to do with creating an archtype. The pom.xml that we want the
archtype to create needs to have certain versions pushed in, but other
things in the pom should be left as is (or allow us to escape it).
The other thing we want to do is push some values INTO a resource that
eventually is a velocity template. (actually, that's what an archtype
is anyway). For those, we need the ability to not have some thing
substituted in.
> Maybe just adding escaping to interpolationfilterreader is much
> simpler than all of this, wdyt?
Probably yes, but would you consider that backwords compatible?
I have no problems with going that route if people don't think it would
seriously impact people.
Dan
> > The other thing I'd like to do is conditional filtering based on
> > whether the version is a SNAPSHOT or not. Kind of like:
> > (pseudocode, not sure on the velocity syntax)
> >
> > #if ${pom.version}.indexOf("SNAPSHOT") != -1
> > version.message=Version ${pom.version} - Use at your own risk.
> > #else
> > version.message=Version ${pom.version}
> > #fi
>
> Why would you want that? :)
>
> -- Kenney
>
> >>> 2) The next option would be to add a filterType configuration
> >>> property onto the resources plugin itself. You would need to
> >>> configure the plugin to use it. Also, it would apply to all
> >>> resources with filtering=true.We could combine this with (1)
> >>> and instead of making "simple" the default if not specified in the
> >>> resource, whatever this option is set to is the default.
> >>
> >> This is a better option. the plugin can be configured with resource
> >> sets, which are just initialized from the pom itself.
> >> perhaps 'src/main/velocity/' could be checked by default and
> >> velocity-copied.
> >
> > The problem is the "Resource" object that the resources plugin uses
> > is maven-model defined. Not something that's extensible as that
> > requires a schema change.I suppose what COULD work well is to
> > add: velocityResources = List
> > configuration to the resources plugin (and if list is empty, look
> > for the default of src/main/velocity) and use that.In that case,
> > "regular" resources can be configured just in build/resources and
> > build/testResources, but the velocity based ones would need a full
> > plugin configuration. A bit inconsistent, but acceptable.
> >
> >
> > After thinking about this a bit more, I wonder if it makes more
> > sense to just create a "maven-velocity-plugin" and ignore resources
> > all-together? That would be super quick to write.(I'd still like
> > to see the escaping issue fixed. :-) We already have the plexus
> > VelocityComponent. Would take very little work to wire it into a
> > plugin.
> >
> >>> Anyway, what are peoples thoughts on this?Any other options?
> >>> What direction do people feel is the best way to proceed? I
> >>> personally would like to go with Option #1 and require Maven 2.0.8
> >>> if you want to use the advanced filtering, but I know some people
> >>> are totally against schema changes.
> >>
> >> Well, if there's a good reason to change the schema then I'm all
> >> for it. Maybe we should just add again to dependencies
> >> and resource sets, so the resource plugin can look at the
> >> resourceset property 'filterType' or something, if it's set.
> >>
> >> Either way, changes to the model won't happen until 2.1.
> >>
> >> So, what's the problem with the filtering?
> >
> > Getting any of the normal pom properties outputted to the target
> > file seems to be impossible.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource filtering thoughts...
Daniel Kulp wrote:
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
Daniel Kulp wrote:
After battling with the braindead resource filtering once again for
the ump-teenth time, I've decided I need to do something about
it
You dissin' my code huh? :)
The main thing I'd like to do is allow use of a better filter engine
(like velocity) that would provide much more flexibility. The
issue is how to do it without breaking all the existing builds that
are out there. Here are my thoughts
I'd very much like to know what the problems are. Probably the fact
that escaping is missing?
Yep. That's the #1 issue.I've completely given up on trying to get
the string "${pom.version}" outputted into the file.
Ok, but why are you filtering a file with that in there? Do you need filtering
at all, or do you only want some things filtered?
You can exclude specific files from filtering; doesn't that solve your problem?
Maybe just adding escaping to interpolationfilterreader is much simpler
than all of this, wdyt?
The other thing I'd like to do is conditional filtering based on whether
the version is a SNAPSHOT or not. Kind of like: (pseudocode, not sure
on the velocity syntax)
#if ${pom.version}.indexOf("SNAPSHOT") != -1
version.message=Version ${pom.version} - Use at your own risk.
#else
version.message=Version ${pom.version}
#fi
Why would you want that? :)
-- Kenney
2) The next option would be to add a filterType configuration
property onto the resources plugin itself. You would need to
configure the plugin to use it. Also, it would apply to all
resources with filtering=true.We could combine this with (1) and
instead of making "simple" the default if not specified in the
resource, whatever this option is set to is the default.
This is a better option. the plugin can be configured with resource
sets, which are just initialized from the pom itself.
perhaps 'src/main/velocity/' could be checked by default and
velocity-copied.
The problem is the "Resource" object that the resources plugin uses is
maven-model defined. Not something that's extensible as that requires
a schema change.I suppose what COULD work well is to add:
velocityResources = List
configuration to the resources plugin (and if list is empty, look for the
default of src/main/velocity) and use that.In that case, "regular"
resources can be configured just in build/resources and
build/testResources, but the velocity based ones would need a full
plugin configuration. A bit inconsistent, but acceptable.
After thinking about this a bit more, I wonder if it makes more sense to
just create a "maven-velocity-plugin" and ignore resources all-together?
That would be super quick to write.(I'd still like to see the
escaping issue fixed. :-) We already have the plexus
VelocityComponent. Would take very little work to wire it into a
plugin.
Anyway, what are peoples thoughts on this?Any other options?
What direction do people feel is the best way to proceed? I
personally would like to go with Option #1 and require Maven 2.0.8
if you want to use the advanced filtering, but I know some people
are totally against schema changes.
Well, if there's a good reason to change the schema then I'm all for
it. Maybe we should just add again to dependencies and
resource sets, so the resource plugin can look at the resourceset
property 'filterType' or something, if it's set.
Either way, changes to the model won't happen until 2.1.
So, what's the problem with the filtering?
Getting any of the normal pom properties outputted to the target file
seems to be impossible.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-plugin-testing-harness 1.1
+1 Arnaud On 09/07/07, Andrew Williams <[EMAIL PROTECTED]> wrote: +1 On 9 Jul 2007, at 00:37, Brian E. Fox wrote: > There have been tons of enhancements to the plugin testing harness > since > the last release in April. Several plugins require the new version > before release. > > > > Tag: > > https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin- > testing- > harness-1.1 > > > > Staged at: > > http://people.apache.org/~brianf/staging-repository > > > > Vote is open for 72hrs, please +1/+0/-1 > > > > +1 > > > > Thanks, > > Brian > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shared JAR component 1.0
+1 Arnaud On 09/07/07, Jesse McConnell <[EMAIL PROTECTED]> wrote: +1 On 7/9/07, John Casey <[EMAIL PROTECTED]> wrote: > +1 > > -john > > > On Jul 4, 2007, at 5:17 AM, Brett Porter wrote: > > > This component is used in the project-info-reports plugin (and is a > > prereq to its next release) and analyses JAR files for Maven > > information and general Java class information. > > > > Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven- > > shared-jar-1.0 > > Staging Repo: http://people.apache.org/~brett/stage-repo/ > > Website/documentation: http://maven.apache.org/shared/maven-shared- > > jar/ > > > > [ ] +1 > > [ ] 0 > > [ ] -1 > > > > 72 hours go! > > > > Cheers, > > Brett > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > > > -- jesse mcconnell [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release eclipse 2.4 (take 2)
+1 Arnaud On 09/07/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: +1 On 7/7/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > It's been about 5 months since an eclipse plugin release and we have > lots of fixes and a handful of enhancements. The issues detected in the > last vote (MECLIPSE-295) have been fixed in the currently staged > plugin-testing-tools 1.0-alpha-2. As such, this release is dependent on > the successful release of the updated tools. > > The site has been updated: > http://maven.apache.org/plugins/maven-eclipse-plugin > > The plugin is staged at: > http://people.apache.org/~brianf/staging-repository > > The tag is at: > http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin- > 2.4/ > > Release Notes - Maven 2.x Eclipse Plugin - Version 2.4: > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001&styleName > =Html&projectId=11133&Create=Create > > ** Bug > * [MECLIPSE-108] - .wtpmodules with version 2.4 for > javax.servlet:servlet-api:2.3 > * [MECLIPSE-109] - .component wb-resource source path incorrect for > ear packaging > * [MECLIPSE-151] - Incorrect name for test sources jars > * [MECLIPSE-198] - EJB version is not resloved > * [MECLIPSE-215] - WTP 1.5 Documentation > * [MECLIPSE-220] - Incorrect eclipse facet information when doing > mvn eclipse:eclipse for war and ejb projects. > * [MECLIPSE-225] - Invalid .classpath Entries. > * [MECLIPSE-231] - Clean mojo assumes that POM projects never have > .project files - this is incorrect > * [MECLIPSE-233] - Manifest attributes incorrectly treated as > case-sensitive > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() > reuses String method argument causing maven-eclipse.xml copy-resources > problems > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the > resolution:=optional directive > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method > * [MECLIPSE-239] - eclipse:eclipse fails to find dependency > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used > in wtp facet > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory > Server to be built > * [MECLIPSE-248] - Tests fail due to incorrectly attempting to use > released plugin version, not locally sandboxed one under test", > * [MECLIPSE-255] - WTP Settings does not use servlet-api version > defined in pom.xml > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in > a Java 5.0 project > * [MECLIPSE-278] - duplicated classpathentries > * [MECLIPSE-279] - PDE projects should be considered java projects > in all cases > * [MECLIPSE-287] - Regression - fails to correctly construct > classpath containing dependencies with classifiers > * [MECLIPSE-295] - Eclipse plugin fails due to missing > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > > ** Improvement > * [MECLIPSE-40] - Multi project dependencies should not require > eclipse project names to be the artifactId > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF > * [MECLIPSE-267] - Resolve version ranges in make-artifacts > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet > version, jsp version, ... possible through pom configuration > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder > creation while executing eclipse:rad > * [MECLIPSE-292] - Behaviour for sources and Javadoc attachement for > dependencies should be consistent > > ** New Feature > * [MECLIPSE-65] - Add contextName parameter to eclipse mojo so a > webtool context name doesn't have to match artifactId/project name. > * [MECLIPSE-119] - Allow custom project name for eclipse projects > * [MECLIPSE-189] - addVersionToProjectName property > * [MECLIPSE-251] - Allows prefixing of eclipse project name > * [MECLIPSE-271] - Ability to skip > > > > Vote is open for 72hrs, please +1/+0/-1 > > > +1 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROT
Re: [VOTE] Promote and release maven-osgi shared library 0.1.0
+1 Arnaud On 09/07/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: fixed in the java classes, the pom missing license is due to the release plugin changes On 7/9/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: > +1 > > Review license header (pom or Maven2OsgiConverter) before the release. > > Cheers, > > Vincent > > 2007/7/9, Carlos Sanchez <[EMAIL PROTECTED]>: > > anyone else? > > > > On 7/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > +1 > > > > > > On 6 Jul 07, at 4:27 PM 6 Jul 07, Carlos Sanchez wrote: > > > > > > > maven-osgi is a shared library for maven to osgi and viceversa common > > > > code, like version conversion. It's used by the felix bundle plugin > > > > and the eclipse plugin. > > > > > > > > https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-osgi > > > > > > > > Tagged in https://svn.apache.org/repos/asf/maven/shared/tags/maven- > > > > osgi-0.1.0 > > > > > > > > -- > > > > I could give you my word as a Spaniard. > > > > No good. I've known too many Spaniards. > > > > -- The Princess Bride > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > I could give you my word as a Spaniard. > > No good. I've known too many Spaniards. > > -- The Princess Bride > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-plugin-testing-tools
+1 Arnaud On 09/07/07, Mark Hobson <[EMAIL PROTECTED]> wrote: +1 Mark On 09/07/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: > +1 > (great work in catching the pom:test bug, I got that problem in the > past without being able to trace it down) > > fabrizio > > On 7/9/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Anyone else? This is required by the eclipse release. > > > > > > > > From: [EMAIL PROTECTED] on behalf of Carlos Sanchez > > Sent: Sat 7/7/2007 5:05 PM > > To: Maven Developers List > > Subject: Re: [VOTE] release maven-plugin-testing-tools > > > > > > > > +1 > > > > On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > > The plugin testing tools had a bug that caused the real build artifacts > > > to become corrupted with the IT test version. This release is required > > > for the eclipse-plugin 2.4 release. > > > > > > Issues fixed: > > > MNG-3095 : maven-plugin-testing-tools causes bad version in deployed > > > artifacts after tests are run > > > MECLIPSE-295 : Eclipse plugin fails due to missing > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > > > MNG-3003 : maven-plugin-testing-tools: Updates for PLXUTILS-31 patches > > > And numerous other improvements without Jira issues > > > > > > Staged at: > > > http://people.apache.org/~brianf/staging-repository > > > > > > Tag: > > > https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing- > > > tools-1.0-alpha-2 > > > > > > Please +1/+0/-1, vote is open for 72hrs. > > > > > > +1 > > > --Brian > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > I could give you my word as a Spaniard. > > No good. I've known too many Spaniards. > > -- The Princess Bride > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-plugin-testing-tools
+1 Mark On 09/07/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: +1 (great work in catching the pom:test bug, I got that problem in the past without being able to trace it down) fabrizio On 7/9/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Anyone else? This is required by the eclipse release. > > > > From: [EMAIL PROTECTED] on behalf of Carlos Sanchez > Sent: Sat 7/7/2007 5:05 PM > To: Maven Developers List > Subject: Re: [VOTE] release maven-plugin-testing-tools > > > > +1 > > On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > The plugin testing tools had a bug that caused the real build artifacts > > to become corrupted with the IT test version. This release is required > > for the eclipse-plugin 2.4 release. > > > > Issues fixed: > > MNG-3095 : maven-plugin-testing-tools causes bad version in deployed > > artifacts after tests are run > > MECLIPSE-295 : Eclipse plugin fails due to missing > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > > MNG-3003 : maven-plugin-testing-tools: Updates for PLXUTILS-31 patches > > And numerous other improvements without Jira issues > > > > Staged at: > > http://people.apache.org/~brianf/staging-repository > > > > Tag: > > https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing- > > tools-1.0-alpha-2 > > > > Please +1/+0/-1, vote is open for 72hrs. > > > > +1 > > --Brian > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-plugin-testing-tools
+1 (great work in catching the pom:test bug, I got that problem in the past without being able to trace it down) fabrizio On 7/9/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: Anyone else? This is required by the eclipse release. From: [EMAIL PROTECTED] on behalf of Carlos Sanchez Sent: Sat 7/7/2007 5:05 PM To: Maven Developers List Subject: Re: [VOTE] release maven-plugin-testing-tools +1 On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The plugin testing tools had a bug that caused the real build artifacts > to become corrupted with the IT test version. This release is required > for the eclipse-plugin 2.4 release. > > Issues fixed: > MNG-3095 : maven-plugin-testing-tools causes bad version in deployed > artifacts after tests are run > MECLIPSE-295 : Eclipse plugin fails due to missing > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > MNG-3003 : maven-plugin-testing-tools: Updates for PLXUTILS-31 patches > And numerous other improvements without Jira issues > > Staged at: > http://people.apache.org/~brianf/staging-repository > > Tag: > https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing- > tools-1.0-alpha-2 > > Please +1/+0/-1, vote is open for 72hrs. > > +1 > --Brian > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] release maven-plugin-testing-tools
Anyone else? This is required by the eclipse release. From: [EMAIL PROTECTED] on behalf of Carlos Sanchez Sent: Sat 7/7/2007 5:05 PM To: Maven Developers List Subject: Re: [VOTE] release maven-plugin-testing-tools +1 On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The plugin testing tools had a bug that caused the real build artifacts > to become corrupted with the IT test version. This release is required > for the eclipse-plugin 2.4 release. > > Issues fixed: > MNG-3095 : maven-plugin-testing-tools causes bad version in deployed > artifacts after tests are run > MECLIPSE-295 : Eclipse plugin fails due to missing > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > MNG-3003 : maven-plugin-testing-tools: Updates for PLXUTILS-31 patches > And numerous other improvements without Jira issues > > Staged at: > http://people.apache.org/~brianf/staging-repository > > Tag: > https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing- > tools-1.0-alpha-2 > > Please +1/+0/-1, vote is open for 72hrs. > > +1 > --Brian > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource filtering thoughts...
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
> Daniel Kulp wrote:
> > After battling with the braindead resource filtering once again for
> > the ump-teenth time, I've decided I need to do something about
> > it
>
> You dissin' my code huh? :)
>
> > The main thing I'd like to do is allow use of a better filter engine
> > (like velocity) that would provide much more flexibility. The
> > issue is how to do it without breaking all the existing builds that
> > are out there. Here are my thoughts
>
> I'd very much like to know what the problems are. Probably the fact
> that escaping is missing?
Yep. That's the #1 issue.I've completely given up on trying to get
the string "${pom.version}" outputted into the file.
The other thing I'd like to do is conditional filtering based on whether
the version is a SNAPSHOT or not. Kind of like: (pseudocode, not sure
on the velocity syntax)
#if ${pom.version}.indexOf("SNAPSHOT") != -1
version.message=Version ${pom.version} - Use at your own risk.
#else
version.message=Version ${pom.version}
#fi
> > 2) The next option would be to add a filterType configuration
> > property onto the resources plugin itself. You would need to
> > configure the plugin to use it. Also, it would apply to all
> > resources with filtering=true.We could combine this with (1) and
> > instead of making "simple" the default if not specified in the
> > resource, whatever this option is set to is the default.
>
> This is a better option. the plugin can be configured with resource
> sets, which are just initialized from the pom itself.
> perhaps 'src/main/velocity/' could be checked by default and
> velocity-copied.
The problem is the "Resource" object that the resources plugin uses is
maven-model defined. Not something that's extensible as that requires
a schema change.I suppose what COULD work well is to add:
velocityResources = List
configuration to the resources plugin (and if list is empty, look for the
default of src/main/velocity) and use that.In that case, "regular"
resources can be configured just in build/resources and
build/testResources, but the velocity based ones would need a full
plugin configuration. A bit inconsistent, but acceptable.
After thinking about this a bit more, I wonder if it makes more sense to
just create a "maven-velocity-plugin" and ignore resources all-together?
That would be super quick to write.(I'd still like to see the
escaping issue fixed. :-) We already have the plexus
VelocityComponent. Would take very little work to wire it into a
plugin.
> > Anyway, what are peoples thoughts on this?Any other options?
> > What direction do people feel is the best way to proceed? I
> > personally would like to go with Option #1 and require Maven 2.0.8
> > if you want to use the advanced filtering, but I know some people
> > are totally against schema changes.
>
> Well, if there's a good reason to change the schema then I'm all for
> it. Maybe we should just add again to dependencies and
> resource sets, so the resource plugin can look at the resourceset
> property 'filterType' or something, if it's set.
>
> Either way, changes to the model won't happen until 2.1.
>
> So, what's the problem with the filtering?
Getting any of the normal pom properties outputted to the target file
seems to be impossible.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resource filtering thoughts...
Daniel Kulp wrote: After battling with the braindead resource filtering once again for the ump-teenth time, I've decided I need to do something about it You dissin' my code huh? :) The main thing I'd like to do is allow use of a better filter engine (like velocity) that would provide much more flexibility. The issue is how to do it without breaking all the existing builds that are out there. Here are my thoughts I'd very much like to know what the problems are. Probably the fact that escaping is missing? 1) Ideally to me, we'd add a "filterType" element to the Resource type in maven-model. It would default to "simple" (the existing implementation) if unspecified. We could support "velocity" and others in the future. This way, a single project could have some resource directories filtering with velocity, others with the old stuff, etc... You also wouldn't need to configure the resources plugin directly just like you don't need to now. The major downside to this is it requires a (backwords compatible) change to the schema and of course would require maven 2.0.8 (assuming it's in place before 2.0.8 is released). 2) The next option would be to add a filterType configuration property onto the resources plugin itself. You would need to configure the plugin to use it. Also, it would apply to all resources with filtering=true.We could combine this with (1) and instead of making "simple" the default if not specified in the resource, whatever this option is set to is the default. This is a better option. the plugin can be configured with resource sets, which are just initialized from the pom itself. perhaps 'src/main/velocity/' could be checked by default and velocity-copied. 3) The other option would be to try something "automatic". Example: if the file ends in ".vm", strip the .vm and filter with velocity. I REALLY don't like this option (and it's also not really backwords compatible). No it isn't.. usually .vm files are used by the application itself so this is definitely not the way. Even files with other extensions may be used by the application itself as velocity templates. Anyway, what are peoples thoughts on this?Any other options? What direction do people feel is the best way to proceed? I personally would like to go with Option #1 and require Maven 2.0.8 if you want to use the advanced filtering, but I know some people are totally against schema changes. Well, if there's a good reason to change the schema then I'm all for it. Maybe we should just add again to dependencies and resource sets, so the resource plugin can look at the resourceset property 'filterType' or something, if it's set. Either way, changes to the model won't happen until 2.1. So, what's the problem with the filtering? -- Kenney - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing maven-release-plugin 2.0-beta-7
On Monday 09 July 2007 04:37, Mark Hobson wrote: > Hi Daniel, > > I'm not overly familiar with that side of the release plugin, so if > someone else fancies reviewing the changes. Does this affect > MRELEASE-83 at all? Since that's the only unresolved issue scheduled > for 2.0-beta-7. Nope. Doesn't touch that side. However, I cannot reproduce MRELEASE-83. I cannot see how, but that may be SCM specific. For my SVN stuff, when I ran: mvn release:prepare -Dusername=dkulp -Dpassword=XX all the svn commands had the correct flags: svn --username dkulp --password * --non-interactive status svn --username dkulp --password * --non-interactive \ commit --file /tmp/maven-scm-872347461.commit \ --targets /tmp/maven-scm-63296-targets svn --username dkulp --password * --non-interactive \ copy --file /tmp/maven-scm-668401696.commit . \ http://url/to/repo/tag svn --username dkulp --password * --non-interactive \ commit --file /tmp/maven-scm-506104864.commit \ --targets /tmp/maven-scm-63297-targets and for mvn release:perform: svn --username dkulp --password * --non-interactive checkout \ http://url/to/repo/tag checkout Dan > > Cheers, > > Mark > > On 07/07/07, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > Mark, > > > > I just committed a start of a fix for this problem. > > > > To not require a new release of plexus-utils, I copied a little bit > > out of CommandLineUtils and into ForkedMavenExecutor for now. > > Longer term, that code should go back into plexus-utils (I'm not a > > committer there). > > > > I've done some basic testing and things seem to work much better. > > gpg plugin properly asks for it's password. gpg output is > > displayed. etc > > > > This MAY also fix MRELEASE-93. Not sure. However, switching to > > the raw streams from the line based buffered IO SHOULD fix that. I > > haven't actually tried that yet. > > > > In any case, could someone more familiar with the code do a quick > > review on it to make sure it's OK? > > > > Thanks! > > Dan > > > > On Saturday 07 July 2007 10:52, Daniel Kulp wrote: > > > Mark, > > > > > > I was looking into the problems with the GPG plugin when run from > > > the release plugin and the problems seem to entirely be problems > > > of the release plugin and Plexus utils. They are showing up in > > > the gpg plugin, but any plugin that tries to do anything > > > interactively would most likely run into the same problems. > > > > > > Issues: > > > 1) System.in - the release manager doesn't feed anything from > > > System.in into the forked process. I tried adding System.in to > > > the CommandLineUtils.executeCommandLine call, but that just causes > > > a hang. CommandLineUtils will wait until the "in" stream is > > > completely consumed (returns -1) before returning. With > > > System.in, that never will happen. > > > > > > 2) Buffered(line style) out - the StreamPumpers use > > > BufferedInputStream.readLine() to pump from one stream to the > > > other. This won't work. Anything that does something (like the > > > release plugin itself) that prompts and then waits for a response > > > on the same line will appear to just "hang" as the prompt will > > > never make it to the screen. > > > > > > Basically, those two issues completely prevent us from being able > > > to un-hard code GPG passphrases from build scripts and such. > > > (unless you set gpg.useagent to true and use an agent) > > > > > > In anycase, MGPG-9 is really a release plugin bug although part of > > > it is due to plexus-utils not providing the support it would need > > > to work properly.Most likely, we'll need to add a method in > > > CommandLineUtils that would just take the raw streams (in/out/err) > > > and do straight byte copy reads without the line buffering. (and > > > once the process completely, stop pumping the in stream) (of > > > course, that would then require another plexus-utils release and > > > then the release plugin would only work with Maven 2.0.6+ with the > > > utils shaded, but that may be minor) I'll poke around more and > > > see if I can come up with something. > > > > > > > > > Dan > > > > > > On Friday 06 July 2007 10:25, Mark Hobson wrote: > > > > Hi, > > > > > > > > There's only one remaining issue, MRELEASE-83, scheduled for > > > > 2.0-beta-7 - is anyone likely to work on this soon, or shall we > > > > defer it until beta-8? I would like to see beta-7 released for > > > > the release POM fixes - they're rather unusable in beta-6. > > > > > > > > Cheers, > > > > > > > > Mark > > > > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > J. Daniel Kulp > > Principal Engineer > > IONA > > P: 781-902-8727C: 508-380-7194 > > [EMAIL PROTECTED] > > http://www.dankulp.com/blog > >
Re: [VOTE] Promote and release maven-osgi shared library 0.1.0
fixed in the java classes, the pom missing license is due to the release plugin changes On 7/9/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: +1 Review license header (pom or Maven2OsgiConverter) before the release. Cheers, Vincent 2007/7/9, Carlos Sanchez <[EMAIL PROTECTED]>: > anyone else? > > On 7/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > +1 > > > > On 6 Jul 07, at 4:27 PM 6 Jul 07, Carlos Sanchez wrote: > > > > > maven-osgi is a shared library for maven to osgi and viceversa common > > > code, like version conversion. It's used by the felix bundle plugin > > > and the eclipse plugin. > > > > > > https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-osgi > > > > > > Tagged in https://svn.apache.org/repos/asf/maven/shared/tags/maven- > > > osgi-0.1.0 > > > > > > -- > > > I could give you my word as a Spaniard. > > > No good. I've known too many Spaniards. > > > -- The Princess Bride > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Promote and release maven-osgi shared library 0.1.0
+1 Review license header (pom or Maven2OsgiConverter) before the release. Cheers, Vincent 2007/7/9, Carlos Sanchez <[EMAIL PROTECTED]>: anyone else? On 7/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > +1 > > On 6 Jul 07, at 4:27 PM 6 Jul 07, Carlos Sanchez wrote: > > > maven-osgi is a shared library for maven to osgi and viceversa common > > code, like version conversion. It's used by the felix bundle plugin > > and the eclipse plugin. > > > > https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-osgi > > > > Tagged in https://svn.apache.org/repos/asf/maven/shared/tags/maven- > > osgi-0.1.0 > > > > -- > > I could give you my word as a Spaniard. > > No good. I've known too many Spaniards. > > -- The Princess Bride > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Promote and release maven-osgi shared library 0.1.0
anyone else? On 7/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: +1 On 6 Jul 07, at 4:27 PM 6 Jul 07, Carlos Sanchez wrote: > maven-osgi is a shared library for maven to osgi and viceversa common > code, like version conversion. It's used by the felix bundle plugin > and the eclipse plugin. > > https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-osgi > > Tagged in https://svn.apache.org/repos/asf/maven/shared/tags/maven- > osgi-0.1.0 > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release eclipse 2.4 (take 2)
+1 On 7/7/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: It's been about 5 months since an eclipse plugin release and we have lots of fixes and a handful of enhancements. The issues detected in the last vote (MECLIPSE-295) have been fixed in the currently staged plugin-testing-tools 1.0-alpha-2. As such, this release is dependent on the successful release of the updated tools. The site has been updated: http://maven.apache.org/plugins/maven-eclipse-plugin The plugin is staged at: http://people.apache.org/~brianf/staging-repository The tag is at: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin- 2.4/ Release Notes - Maven 2.x Eclipse Plugin - Version 2.4: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001&styleName =Html&projectId=11133&Create=Create ** Bug * [MECLIPSE-108] - .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3 * [MECLIPSE-109] - .component wb-resource source path incorrect for ear packaging * [MECLIPSE-151] - Incorrect name for test sources jars * [MECLIPSE-198] - EJB version is not resloved * [MECLIPSE-215] - WTP 1.5 Documentation * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn eclipse:eclipse for war and ejb projects. * [MECLIPSE-225] - Invalid .classpath Entries. * [MECLIPSE-231] - Clean mojo assumes that POM projects never have .project files - this is incorrect * [MECLIPSE-233] - Manifest attributes incorrectly treated as case-sensitive * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses String method argument causing maven-eclipse.xml copy-resources problems * [MECLIPSE-236] - eclipse:make-artifacts should preserve the resolution:=optional directive * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method * [MECLIPSE-239] - eclipse:eclipse fails to find dependency org.apache.maven.plugins:maven-eclipse-plugin:pom:test * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in wtp facet * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server to be built * [MECLIPSE-248] - Tests fail due to incorrectly attempting to use released plugin version, not locally sandboxed one under test", * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined in pom.xml * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a Java 5.0 project * [MECLIPSE-278] - duplicated classpathentries * [MECLIPSE-279] - PDE projects should be considered java projects in all cases * [MECLIPSE-287] - Regression - fails to correctly construct classpath containing dependencies with classifiers * [MECLIPSE-295] - Eclipse plugin fails due to missing org.apache.maven.plugins:maven-eclipse-plugin:pom:test ** Improvement * [MECLIPSE-40] - Multi project dependencies should not require eclipse project names to be the artifactId * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF * [MECLIPSE-267] - Resolve version ranges in make-artifacts * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet version, jsp version, ... possible through pom configuration * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder creation while executing eclipse:rad * [MECLIPSE-292] - Behaviour for sources and Javadoc attachement for dependencies should be consistent ** New Feature * [MECLIPSE-65] - Add contextName parameter to eclipse mojo so a webtool context name doesn't have to match artifactId/project name. * [MECLIPSE-119] - Allow custom project name for eclipse projects * [MECLIPSE-189] - addVersionToProjectName property * [MECLIPSE-251] - Allows prefixing of eclipse project name * [MECLIPSE-271] - Ability to skip Vote is open for 72hrs, please +1/+0/-1 +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Platform farm
<> Just so you know, VMware Server is free. I have used it to set up testing environments, seems to work pretty well. http://www.vmware.com/products/free_virtualization.html -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shared JAR component 1.0
+1 On 7/9/07, John Casey <[EMAIL PROTECTED]> wrote: +1 -john On Jul 4, 2007, at 5:17 AM, Brett Porter wrote: > This component is used in the project-info-reports plugin (and is a > prereq to its next release) and analyses JAR files for Maven > information and general Java class information. > > Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven- > shared-jar-1.0 > Staging Repo: http://people.apache.org/~brett/stage-repo/ > Website/documentation: http://maven.apache.org/shared/maven-shared- > jar/ > > [ ] +1 > [ ] 0 > [ ] -1 > > 72 hours go! > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john -- jesse mcconnell [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shared JAR component 1.0
+1 -john On Jul 4, 2007, at 5:17 AM, Brett Porter wrote: This component is used in the project-info-reports plugin (and is a prereq to its next release) and analyses JAR files for Maven information and general Java class information. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven- shared-jar-1.0 Staging Repo: http://people.apache.org/~brett/stage-repo/ Website/documentation: http://maven.apache.org/shared/maven-shared- jar/ [ ] +1 [ ] 0 [ ] -1 72 hours go! Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: svn commit: r553253 - /maven/components/trunk/maven-artifact/src/test/java/org/apache/maven/artifact/resolver/DefaultArtifactCollectorTest.java
I'll update asap and give it another shot. Thanks! -john On Jul 6, 2007, at 8:39 PM, Mark Hobson wrote: On 06/07/07, John Casey <[EMAIL PROTECTED]> wrote: t looks like this has broken the trunk build. I get compiler errors now: [java] /Users/jdcasey/workspace/maven/components/maven- artifact/ src/test/java/org/apache/maven/artifact/resolver/ DefaultArtifactCollectorTest.java:[674,25] cannot find symbol [java] symbol : method createArtifact (java.lang.String,java.lang.String) [java] location: class org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest [java] [java] /Users/jdcasey/workspace/maven/components/maven- artifact/ src/test/java/org/apache/maven/artifact/resolver/ DefaultArtifactCollectorTest.java:[676,8] cannot find symbol [java] symbol : method createArtifact (java.lang.String,java.lang.String) [java] location: class org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest Mark, can you roll this back, or fix it? Apologies, try again, that'll teach me to blindly merge :) Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: [VOTE] Graduate maven-patch-plugin from sandbox and release version 1.0
Yes, the idea was to provide the materials necessary for the code grant (since it's coming over from codehaus). I'm not an ASF member, so (according to the IP pages) all I can do is get the materials together for someone else to submit. Once we've cleared any IP hurdles, I'll clean those out. -john On Jul 9, 2007, at 7:02 AM, Vincent Siveton wrote: +1 I guess that maven-patch-plugin.originals.* will be removed from the trunk. Cheers, Vincent 2007/7/6, John Casey <[EMAIL PROTECTED]>: Hi all, Jesse and I have been working on a patch plugin that I migrated over from mojo.codehaus.org into the ASF sandbox, and we feel it's ready for a release. I've prepared the documentation for a code grant on this project, and all the appropriate information should be committed in the plugin directory. The plugin is stable, has decent documentation, and even an integration-test suite. Therefore, I'd like to call a vote to graduate the patch plugin from the Maven sandbox, and do a 1.0 release. Please +1/+0/-1. I'll let this go for 72 hours. The release is staged at: http://people.apache.org/~jdcasey/stage/repo (repository) http://people.apahce.org/~jdcasey/stage/sites/maven-patch-plugin (site) Here's my +1. Thanks to Jesse for helping me get the plugin to this point. -john --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: [VOTE] release maven-plugin-testing-harness 1.1
+1 On 9 Jul 2007, at 00:37, Brian E. Fox wrote: There have been tons of enhancements to the plugin testing harness since the last release in April. Several plugins require the new version before release. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin- testing- harness-1.1 Staged at: http://people.apache.org/~brianf/staging-repository Vote is open for 72hrs, please +1/+0/-1 +1 Thanks, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate maven-patch-plugin from sandbox and release version 1.0
+1 - Joakim John Casey wrote: Hi all, Jesse and I have been working on a patch plugin that I migrated over from mojo.codehaus.org into the ASF sandbox, and we feel it's ready for a release. I've prepared the documentation for a code grant on this project, and all the appropriate information should be committed in the plugin directory. The plugin is stable, has decent documentation, and even an integration-test suite. Therefore, I'd like to call a vote to graduate the patch plugin from the Maven sandbox, and do a 1.0 release. Please +1/+0/-1. I'll let this go for 72 hours. The release is staged at: http://people.apache.org/~jdcasey/stage/repo (repository) http://people.apahce.org/~jdcasey/stage/sites/maven-patch-plugin (site) Here's my +1. Thanks to Jesse for helping me get the plugin to this point. -john --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john -- - Joakim Erdfelt [EMAIL PROTECTED] Open Source Software (OSS) Developer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shared JAR component 1.0
+1 Brett Porter wrote: This component is used in the project-info-reports plugin (and is a prereq to its next release) and analyses JAR files for Maven information and general Java class information. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven-shared-jar-1.0 Staging Repo: http://people.apache.org/~brett/stage-repo/ Website/documentation: http://maven.apache.org/shared/maven-shared-jar/ [ ] +1 [ ] 0 [ ] -1 72 hours go! Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - Joakim Erdfelt [EMAIL PROTECTED] Open Source Software (OSS) Developer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] release maven-enforcer-plugin 1.0-alpha-3 and maven-enforcer-rule-api 1.0-alpha-2
+1 Vincent 2007/7/8, Brian E. Fox <[EMAIL PROTECTED]>: Last release vote this weekend, I promise ;-) The rule api is used by the plugin and is included with this vote. The only change was to the pom to remove an unnecessary dependency. This release contains a few small fixes and several new enforcer rules. The site has been updated with info about all the new rules: * bannedDependencies - enforces that excluded dependencies aren't included. * evaluateBeanshell - evaluates a beanshell script. * noSnapshots - enforces that no snapshots are included. http://maven.apache.org/plugins/maven-enforcer-plugin Tag: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-enforcer-plugi n-1.0-alpha-3 Staged at: http://people.apache.org/~brianf/staging-repository Release Notes - Maven 2.x Enforcer Plugin - Version 1.0-alpha-3 ** Bug * [MENFORCER-4] - Typos in Version Range Specification document * [MENFORCER-9] - Exception in java rule when using Apple JDK 6 Developer Preview ** Improvement * [MENFORCER-6] - add optional message to rules ** New Feature * [MENFORCER-5] - Add property verification to the enforcer plugin * [MENFORCER-7] - new beanshell expression rule * [MENFORCER-8] - Ability to disallow groups of deps Vote is open for the usual 72 hrs, please +1/+0/-1 +1 Thanks, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate maven-patch-plugin from sandbox and release version 1.0
+1 I guess that maven-patch-plugin.originals.* will be removed from the trunk. Cheers, Vincent 2007/7/6, John Casey <[EMAIL PROTECTED]>: Hi all, Jesse and I have been working on a patch plugin that I migrated over from mojo.codehaus.org into the ASF sandbox, and we feel it's ready for a release. I've prepared the documentation for a code grant on this project, and all the appropriate information should be committed in the plugin directory. The plugin is stable, has decent documentation, and even an integration-test suite. Therefore, I'd like to call a vote to graduate the patch plugin from the Maven sandbox, and do a 1.0 release. Please +1/+0/-1. I'll let this go for 72 hours. The release is staged at: http://people.apache.org/~jdcasey/stage/repo (repository) http://people.apahce.org/~jdcasey/stage/sites/maven-patch-plugin (site) Here's my +1. Thanks to Jesse for helping me get the plugin to this point. -john --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-plugin-testing-harness 1.1
+1 Needs to review/remove TODO in the code and specify default value in the javadoc (MNG-3098) Cheers, Vincent 2007/7/8, Brian E. Fox <[EMAIL PROTECTED]>: There have been tons of enhancements to the plugin testing harness since the last release in April. Several plugins require the new version before release. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing- harness-1.1 Staged at: http://people.apache.org/~brianf/staging-repository Vote is open for 72hrs, please +1/+0/-1 +1 Thanks, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shared JAR component 1.0
+1 Vincent 2007/7/8, Brian E. Fox <[EMAIL PROTECTED]>: +1 -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:18 AM To: Maven Developers List Subject: [vote] Release Maven Shared JAR component 1.0 This component is used in the project-info-reports plugin (and is a prereq to its next release) and analyses JAR files for Maven information and general Java class information. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven-shared- jar-1.0 Staging Repo: http://people.apache.org/~brett/stage-repo/ Website/documentation: http://maven.apache.org/shared/maven-shared-jar/ [ ] +1 [ ] 0 [ ] -1 72 hours go! Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] release eclipse 2.4 (take 2)
2.4 is really more mature than previous versions. It has been quite a time since 2.3 Definitly a +1 here (though just a user one). Denis. > -Message d'origine- > De : Mark Hobson [mailto:[EMAIL PROTECTED] > Envoyé : Monday, July 09, 2007 10:45 AM > À : Maven Developers List > Objet : Re: [VOTE] release eclipse 2.4 (take 2) > > On 09/07/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > > I think this is where I got to when I looked into it last > week. I'm > > cool to fix this for 2.5, so negate my -1 and go for it. > > Trunk tests pass on Windows with spaces in path! Thanks for > that Brian. > > Mark > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin: readonly "filters" parameter can break a multimodule build
OK, I will work on this, then. Cheers Fabrice On 7/6/07, John Casey <[EMAIL PROTECTED]> wrote: That sounds like a fine idea to me. I commented on the issue, too, fwiw. Thanks, -john On Jul 6, 2007, at 5:55 AM, Fabrice Bellingard wrote: > I got this problem while trying to make an assembly, with filtered > files, > from a root project. I created an issue on JIRA with an example: > http://jira.codehaus.org/browse/MASSEMBLY-226 > > If the "filters" parameter would not be readonly, then this bug > would be > obsolete. > Should I modify this? I ask the question because it seems that for > some > reason, this param became readonly whereas it didn't use to be at > first. > > Cheers! > Fabrice --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: [VOTE] release eclipse 2.4 (take 2)
On 09/07/07, Mark Hobson <[EMAIL PROTECTED]> wrote: I think this is where I got to when I looked into it last week. I'm cool to fix this for 2.5, so negate my -1 and go for it. Trunk tests pass on Windows with spaces in path! Thanks for that Brian. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing maven-release-plugin 2.0-beta-7
Hi Daniel, I'm not overly familiar with that side of the release plugin, so if someone else fancies reviewing the changes. Does this affect MRELEASE-83 at all? Since that's the only unresolved issue scheduled for 2.0-beta-7. Cheers, Mark On 07/07/07, Daniel Kulp <[EMAIL PROTECTED]> wrote: Mark, I just committed a start of a fix for this problem. To not require a new release of plexus-utils, I copied a little bit out of CommandLineUtils and into ForkedMavenExecutor for now. Longer term, that code should go back into plexus-utils (I'm not a committer there). I've done some basic testing and things seem to work much better. gpg plugin properly asks for it's password. gpg output is displayed. etc This MAY also fix MRELEASE-93. Not sure. However, switching to the raw streams from the line based buffered IO SHOULD fix that. I haven't actually tried that yet. In any case, could someone more familiar with the code do a quick review on it to make sure it's OK? Thanks! Dan On Saturday 07 July 2007 10:52, Daniel Kulp wrote: > Mark, > > I was looking into the problems with the GPG plugin when run from the > release plugin and the problems seem to entirely be problems of the > release plugin and Plexus utils. They are showing up in the gpg > plugin, but any plugin that tries to do anything interactively would > most likely run into the same problems. > > Issues: > 1) System.in - the release manager doesn't feed anything from > System.in into the forked process. I tried adding System.in to the > CommandLineUtils.executeCommandLine call, but that just causes a hang. > CommandLineUtils will wait until the "in" stream is completely > consumed (returns -1) before returning. With System.in, that never > will happen. > > 2) Buffered(line style) out - the StreamPumpers use > BufferedInputStream.readLine() to pump from one stream to the other. > This won't work. Anything that does something (like the release > plugin itself) that prompts and then waits for a response on the same > line will appear to just "hang" as the prompt will never make it to > the screen. > > Basically, those two issues completely prevent us from being able to > un-hard code GPG passphrases from build scripts and such. (unless > you set gpg.useagent to true and use an agent) > > In anycase, MGPG-9 is really a release plugin bug although part of it > is due to plexus-utils not providing the support it would need to work > properly.Most likely, we'll need to add a method in > CommandLineUtils that would just take the raw streams (in/out/err) and > do straight byte copy reads without the line buffering. (and once the > process completely, stop pumping the in stream) (of course, that > would then require another plexus-utils release and then the release > plugin would only work with Maven 2.0.6+ with the utils shaded, but > that may be minor) I'll poke around more and see if I can come up > with something. > > > Dan > > On Friday 06 July 2007 10:25, Mark Hobson wrote: > > Hi, > > > > There's only one remaining issue, MRELEASE-83, scheduled for > > 2.0-beta-7 - is anyone likely to work on this soon, or shall we > > defer it until beta-8? I would like to see beta-7 released for the > > release POM fixes - they're rather unusable in beta-6. > > > > Cheers, > > > > Mark > > > > > >- To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release eclipse 2.4 (take 2)
On 08/07/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
The problem is in the invoker. When the pom is specified as is in the
case of the plugin tools, the -F command line is used to specify it:
if ( !"pom.xml".equals( pom.getName() ) )
{
logger
.debug( "Specified POM file is not named
\'pom.xml\'. Using the \'-f\' command-line option to accommodate
non-standard filename..." );
// FIXME: Handle quotes in localRepo directory path...
cli.createArgument().setLine( "-f " + pom.getName() );
}
This is an edge case in the tests and doesn't affect the eclipse plugin
functionality, thus I'm of the opinion that the release should continue.
To fix this would require a release of the 2.0.7 invoker and would
effectively kill the eclipse release for a while; I need to move to some
other things for a while and won't have the time to do it myself.
I think this is where I got to when I looked into it last week. I'm
cool to fix this for 2.5, so negate my -1 and go for it.
Cheers,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
