allow nested search parameters
--
Key: MRM-54
URL: http://jira.codehaus.org/browse/MRM-54
Project: Maven Repository Manager
Type: Task
Components: indexing
Reporter: Edwin Punzalan
Assigned to: Edwin Punzalan
Search parameters
[ http://jira.codehaus.org/browse/MASSEMBLY-47?page=all ]
Brett Porter closed MASSEMBLY-47:
-
Resolution: Fixed
> Assembly task does not include modules
> --
>
> Key: MASSEMBLY-47
> URL: http://ji
[ http://jira.codehaus.org/browse/MASSEMBLY-47?page=all ]
Brett Porter updated MASSEMBLY-47:
--
Assign To: Brett Porter
Version: 2.0
Fix Version: 2.1
> Assembly task does not include modules
> --
>
>
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_54729 ]
Dan Tran commented on MRELEASE-66:
--
cl.createArgument().setLine( "-DperformRelease=true" );
triggers super pom performRelease Profile which will generate those bundle
http://maven.a
Source and Javadoc bundles should be optional
-
Key: MRELEASE-66
URL: http://jira.codehaus.org/browse/MRELEASE-66
Project: Maven 2.x Release Plugin
Type: Bug
Environment: xp
Reporter: Dan Tran
The current release pl
[ http://jira.codehaus.org/browse/MRELEASE-40?page=comments#action_54728 ]
Dan Tran commented on MRELEASE-40:
--
org.codehaus.mojo's dependency-maven-plugin ran into similar problem where
the local username and svn username are not the same. For this case
we
[ http://jira.codehaus.org/browse/MASSEMBLY-25?page=comments#action_54727 ]
Dan Tran commented on MASSEMBLY-25:
---
Jochen,
could you stay in maven-assembly-plugin and do a diff again? Your patch has
your full path.
> Support for multiple assembly descrip
Please add this bundle to the Maven2 repository
---
Key: MAVENUPLOAD-657
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-657
Project: maven-upload-requests
Type: Task
Reporter: Thomas Bentzen
Attachments: dynpageplus
[ http://jira.codehaus.org/browse/MEV-275?page=all ]
David Blevins updated MEV-275:
--
Attachment: castor-1.0M1.patch
> Castor dependencies
> ---
>
> Key: MEV-275
> URL: http://jira.codehaus.org/browse/MEV-275
> Project:
Castor dependencies
---
Key: MEV-275
URL: http://jira.codehaus.org/browse/MEV-275
Project: Maven Evangelism
Type: Improvement
Components: Dependencies
Reporter: David Blevins
Added some of the missing deps for castor to run
--
This messag
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060103.014500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060103.014500.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060103.011501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060103.011501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MEV-272?page=all ]
Edwin Punzalan closed MEV-272:
--
Assign To: Edwin Punzalan (was: Carlos Sanchez)
Resolution: Fixed
Thanks.
Relocation pom created.
NOTE: May take up to 4 hours for the fix to reach central re
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060103.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060103.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MASSEMBLY-18?page=all ]
Dan Tran closed MASSEMBLY-18:
-
Resolution: Duplicate
this is a duplicate of MASSEMBLY-46 which has more info
> Assembly plugin does'nt use classifier for dependencies
> -
[ http://jira.codehaus.org/browse/MPGENAPP-16?page=all ]
Lukas Theussl closed MPGENAPP-16:
-
Resolution: Won't Fix
Updated documentation.
> Use of template.jelly does not work and is not documented.
>
Is anyone looking into why these intermittently fail?
[EMAIL PROTECTED] wrote:
> Log:
> http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060103.003000.txt
>
> -
> To unsubscribe, e-mail: [EMAIL PROTEC
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060103.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Dan,
I believe this is slightly different - I am trying to set a field for a complex
type ( the field is of type 'java.lang.Class'). The complex type itself gets
instantiated fine but the issue comes when attempting to setup the field. Brett
drilled down the issue to be missing convertor im
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
--
Fix Version: 2.0.3
> M1 snapshots on legacy repos can not be used with m2
>
>
> Key: MNG-1908
> URL:
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060103.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MASSEMBLY-48?page=comments#action_54719 ]
Dan Tran commented on MASSEMBLY-48:
---
This is fixed in maven-2.0.1, see MASSEMBLY-49
> Wrong attached assembly extension
> -
>
> Key: MASSEM
[ http://jira.codehaus.org/browse/MASSEMBLY-49?page=comments#action_54718 ]
Dan Tran commented on MASSEMBLY-49:
---
This is fixed in maven-2.0.1 where maven-project's AttachedArtifact has the fix
to accept attched artifact without specifier
> InvalidArtifact
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54717 ]
Grégory Joseph commented on MNG-1912:
-
Hmmm, that could be pretty annoying, but I guess I'd play with exclusions in
that case. I reckon it's pretty clumsy - OTOH, in my particular ca
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54716 ]
Brett Porter commented on MNG-1912:
---
Ivy has its own structure, but for 90% of its jars, it leverages the Maven 1
repo.
The problem you will encounter is if you depend on an Ivy snap
I think i ran to this before. The configuraiton object must be in the same
packge of your mojo.
Not sure if this helps thou.
-Dan
On 1/2/06, Rinku <[EMAIL PROTECTED]> wrote:
>
> Hi ,
>
> I did relevant updates to m2 sources on local and updated m2 install for
> plexus-container-default verison
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54715 ]
Grégory Joseph commented on MNG-1912:
-
> They are unlikely to be the same over time. We are moving to dotted group IDs
> and since Ivy completely leverages > the Maven 1 repo, they g
Good point. It's probably looking in the plexus classloader.
I'd need to investigate further how to get the correct classloader. If
you'd like to do so yourself, the class to change is
plexus/plexus-containers/plexus-container-default/src/main/java/org/codehaus/plexus/component/configurator/basic/
Hi ,
I did relevant updates to m2 sources on local and updated m2 install for
plexus-container-default verison 1.0-alpha-10-SNAPSHOT. But still running into a
ClassNotFound error. Looks like its coming from Classworld libs.
I have posted the stacktrace at:
http://www.rafb.net/paste/results/tk
javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
--
Key: MJAVADOC-40
URL: http://jira.codehaus.org/browse/MJAVADOC-40
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Brian Fo
It's the doubt I have actually.
We already publish project sources in the dist plugin.
I don't like to create a new project (we have already enough plugins to
maintain in m1) but it could be a good choice to mimic m2.
Arnaud
On 1/2/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
> +0
>
> Shouldn'
[ http://jira.codehaus.org/browse/MSITE-66?page=comments#action_54710 ]
Dennis Lundberg commented on MSITE-66:
--
Positioning should really be for the footer. I've been playing around with
default-site.vm, but am having trouble reading in values from the
I thought to jar, install and deploy.
I don't know if there's an interest to manually download it. It can be done
with a dependency.
I'll take a look at the m2 plugin to mimic it.
Arnaud
On 1/2/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
> +1
>
> to mimic what we are able to do with m2 it
Add maven-jaxme-plugin to list of plugins
-
Key: MNG-1913
URL: http://jira.codehaus.org/browse/MNG-1913
Project: Maven 2
Type: Improvement
Components: documentation - general
Versions: 2.0.1
Reporter: Jochen Wi
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54709 ]
Brett Porter commented on MNG-1912:
---
yes, we could do it without transitive deps.
While the groupIds and organization have the same purpose, the fact that they
don't match will mean t
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060102.22.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.22.txt
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54708 ]
Elliotte Rusty Harold commented on MAVEN-1345:
--
The AElfred parser is indeed the problem I was referring to. If you pull it out
of the JAR file, dom4j 1.4 should be licens
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54706 ]
Grégory Joseph commented on MNG-1912:
-
s/first/first sight/
s/seems/seemed/
s/make/map/
Jeez, I need a proof-reader.
> Support for ivy repositories
>
>
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54705 ]
Grégory Joseph commented on MNG-1912:
-
Isn't it possible to implement support for retrieving the main artifacts from
an ivy-repository without necessarily enabling transitive depende
There is no plexus converter for String -> Class. We should probably
have one, so I'll add it now.
You'll need to use a String and do the forName yourself in the mean time.
- Brett
Rahul Thakur wrote:
> Hi,
>
> I am following the mini guide to set up a complex mapping for a Mojo.
> http://maven
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.213000.txt
Hi,
I am following the mini guide to set up a complex mapping for a Mojo.
http://maven.apache.org/guides/mini/guide-configuring-plugins.html
The POJO that models the complex type for Mojo configuration has a field
'implementation' of type java.lang.Class.
When I run the Mojo, I get an error:
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54704 ]
Brett Porter commented on MAVEN-1345:
-
We should just stay on 1.4, at least until Jaxen releases 1.1 and Jelly
upgrades.
> Upgrade to dom4j 1.4
>
>
>
[ http://jira.codehaus.org/browse/MASSEMBLY-47?page=comments#action_54703 ]
Yuri Schimke commented on MASSEMBLY-47:
---
Yes, thats exactly what I want. to include all artifacts and dependencies.
The bug report is just that, I needed to directly include a
[ http://jira.codehaus.org/browse/MNG-1911?page=all ]
Brett Porter updated MNG-1911:
--
Fix Version: 2.0.3
> Building plugins with extensions in a reactor fails
> ---
>
> Key: MNG-1911
> URL: h
[ http://jira.codehaus.org/browse/MASSEMBLY-47?page=comments#action_54702 ]
Brett Porter commented on MASSEMBLY-47:
---
Maven doesn't guess that modeA/target/*.jar is actually a Mavne project with
dependencies, its just a JAR.
What you want is to automat
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54701 ]
Stéphane Toussaint commented on MECLIPSE-47:
Ok, I just thought that 1.0 was the default...
Thanks
> Planning support for wtp 1.0
>
>
>
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.21.txt
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54700 ]
Brett Porter commented on MNG-1912:
---
this is not just another layout but an entirely different resolver:
- we'd need to be able to map the ivy "organization" to maven "group id"
- we'd
still thinking about the best way to deal with this. We don't want to
lock the site into a specific version of a plugin every time - it should
be the latest, but we also don't want to use snapshots under some
circumstances.
Basically, I just build the plugins I am working on and am prepared to
dea
It was fixed a while ago, but has not been released.
- Brett
Vincent Massol wrote:
>
>> -Original Message-
>> From: Vincent Massol [mailto:[EMAIL PROTECTED]
>> Sent: lundi 2 janvier 2006 15:55
>> To: 'Maven Developers List'
>> Subject: RE: need help for deploying the clover plugin v2.0
>
Snapshot is a snapshot. We should always have the latest out there.
Jason van Zyl wrote:
> Hi,
>
> A fellow in IRC is asking if we can deploy the external-ssh provider and
> was just wondering if there's any reason why we might not want to deploy
> a snapshot. I know the scp/ssh is being generall
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54699 ]
Rahul Thakur commented on MECLIPSE-47:
--
Maven-Eclipse-Plugin by default generates an Eclipse project targeted at WTP
0.7 (refer to Fabrizio's comments in the thread above).
The
Hi Brian,
Assembly now can do that. Just bind assembly:attached mojo to
package phase. However this feature is not fully functional yet.
Please check JIRA.
-Dan
On 1/2/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> Can the assembly plugin take part in the normal lifecycle in the current
> rel
Hi,
A fellow in IRC is asking if we can deploy the external-ssh provider and
was just wondering if there's any reason why we might not want to deploy
a snapshot. I know the scp/ssh is being generally flaky lately and
didn't want to make things worse.
--
jvz.
Jason van Zyl
jason at maven.or
Can the assembly plugin take part in the normal lifecycle in the current
release (in the past it couldn't)? As I see it, that is a stumbling
block for a lot of people. If this can't or won't be changed, then
spinning off some limited functionality into a separate mojo may make
sense.
-Origina
+1 definitely.
On 1/2/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> It seems useful for some users to have a maven-sources-plugin for m1.
> http://jira.codehaus.org/browse/MAVEN-1736
> Are you agree if we add it in the m1 plugins ?
>
> [ ] +1 - It seems to be a good idea.
>
Arnaud HERITIER wrote:
Hi all,
It seems useful for some users to have a maven-sources-plugin for m1.
http://jira.codehaus.org/browse/MAVEN-1736
Are you agree if we add it in the m1 plugins ?
[ ] +1 - It seems to be a good idea.
[ ] +0 - Don't know
[ ] -1 - No, I prefer .
+1
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: lundi 2 janvier 2006 15:55
> To: 'Maven Developers List'
> Subject: RE: need help for deploying the clover plugin v2.0
>
>
>
> > -Original Message-
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> >
+0
Shouldn't this be part of the dist plugin? We'd just have to add some
goals like dist:source-deploy, dist:source-jar, etc?
-Lukas
Arnaud HERITIER wrote:
Hi all,
It seems useful for some users to have a maven-sources-plugin for m1.
http://jira.codehaus.org/browse/MAVEN-1736
Are you
+1
to mimic what we are able to do with m2 it should include the
following goals/tags:
jar
install
deploy
download
is this what you are planning to include in the plugin?
fabrizio
On 1/2/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> It seems useful for some users to have a mav
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.173000.txt
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54697 ]
Stéphane Toussaint commented on MECLIPSE-47:
After reading this thread, I try to test the svn version with a fresh install
of WTP 1.0 (wtp-all-in-one-sdk-1.0-win32.zip).
A
problem with scm url without username
-
Key: MRELEASE-65
URL: http://jira.codehaus.org/browse/MRELEASE-65
Project: Maven 2.x Release Plugin
Type: Bug
Environment: maven version is 2.0.1
Reporter: Miguel Griffa
I have the fo
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060102.163001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060102.163001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54695 ]
Grégory Joseph commented on MNG-1912:
-
Well, seems to me their ivy built snapshots aren't, at least, and that's those
I currently need.
Doesn't the request makes sense, generally, th
[ http://jira.codehaus.org/browse/MNG-1912?page=comments#action_54694 ]
Carlos Sanchez commented on MNG-1912:
-
opensymphony has already a maven repository that it's automatically sync'd to
ibiblio
> Support for ivy repositories
> ---
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=comments#action_54693 ]
Carlos Sanchez commented on MSUREFIRE-34:
-
You probably have something wrong locally with XMLReporter.java, delete and
checkout again, because it's compiling for me
> surefi
Support for ivy repositories
Key: MNG-1912
URL: http://jira.codehaus.org/browse/MNG-1912
Project: Maven 2
Type: Wish
Components: Artifacts and Repositories
Versions: 2.0.1
Reporter: Grégory Joseph
Hi,
It'd be nice if m
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060102.161501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060102.161501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=comments#action_54692 ]
Leung Man-Chi commented on MSUREFIRE-34:
i just did a $svn update $mvn clean , during compile, I encountered error
[12:26 am]~/Java/workspace-maven2/surefire/surefire$mvn com
[ http://jira.codehaus.org/browse/SUREFIRE-25?page=comments#action_54690 ]
Carlos Sanchez commented on SUREFIRE-25:
Files are created in SurefireBooter
I get them although test succeed with forkmode pertest
> surefire property droppings in fork mode
+1
Emmanuel
Arnaud HERITIER a écrit :
Hi all,
It seems useful for some users to have a maven-sources-plugin for m1.
http://jira.codehaus.org/browse/MAVEN-1736
Are you agree if we add it in the m1 plugins ?
[ ] +1 - It seems to be a good idea.
[ ] +0 - Don't know
[ ] -1 - No, I pre
[ http://jira.codehaus.org/browse/SUREFIRE-25?page=all ]
Carlos Sanchez moved MSUREFIRE-36 to SUREFIRE-25:
-
Fix Version: (was: 2.1.2)
Complexity: Intermediate
Workflow: jira (was: Maven)
Key: SUREFIRE-25 (was:
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060102.16.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.16.txt
[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=all ]
Carlos Sanchez closed MSUREFIRE-20:
---
Assign To: Carlos Sanchez
Resolution: Fixed
Already fixed
integration test added to plugin
> forkMode=pertest fails to call setUp
> --
Hi all,
It seems useful for some users to have a maven-sources-plugin for m1.
http://jira.codehaus.org/browse/MAVEN-1736
Are you agree if we add it in the m1 plugins ?
[ ] +1 - It seems to be a good idea.
[ ] +0 - Don't know
[ ] -1 - No, I prefer .
Arnaud
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=comments#action_54687 ]
Carlos Sanchez commented on MSUREFIRE-34:
-
you can build from svn or wait for a release of surefire
> surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5 xml
Building plugins with extensions in a reactor fails
---
Key: MNG-1911
URL: http://jira.codehaus.org/browse/MNG-1911
Project: Maven 2
Type: Bug
Versions: 2.0.1
Reporter: Guillaume Nodet
Priority: Critica
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060102.153000.txt
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=comments#action_54686 ]
Leung Man-Chi commented on MSUREFIRE-34:
hi,
i was informed from jira that this issues is closed
do u mean that it is an duplicate of (SUREFIRE18)?
can advise on the action t
[ http://jira.codehaus.org/browse/MSUREFIRE-37?page=all ]
Carlos Sanchez closed MSUREFIRE-37:
---
Assign To: Carlos Sanchez
Resolution: Fixed
> Remove or fix strange "battery = null" messages displayed on the console
> --
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=all ]
Carlos Sanchez closed MSUREFIRE-34:
---
Assign To: Carlos Sanchez (was: Jason van Zyl)
Resolution: Duplicate
Fix Version: (was: 2.1.2)
> surefire-report-plugin 2.1 is having F
That would be good!
Thanks,
Stéphane
On 1/2/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> It's quite easy to create a custom artifact handler [1] to deploy sources on
> the repository with a compatible layout for m2.
> But where will we add it ? We don't have a plugin which deploy sources
> ac
It's quite easy to create a custom artifact handler [1] to deploy sources on
the repository with a compatible layout for m2.
But where will we add it ? We don't have a plugin which deploy sources
actually. We have the distribution plugin but it deploys all the project.
Where could we add it ?
I can
dan tran wrote:
I still don't understand. The assembly plugin is already released! :)
Do you mean the wait for the 2.1 release?
It has been 2 and half months. ;-) Is it time a for a new release?
Any how, I agree that It does not look right when there are 2 similar
plugins.
Agreed, I think
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 2 janvier 2006 11:21
> To: Maven Developers List
> Subject: Re: need help for deploying the clover plugin v2.0
>
> Vincent Massol wrote:
> > Hi there,
> >
> > I'm trying to deploy the clover plugin v2.0 but
[
http://jira.codehaus.org/browse/MAVENUPLOAD-644?page=comments#action_54684 ]
Carlos Sanchez commented on MAVENUPLOAD-644:
mmm, maven2 plugins have to go in a different way, I've uploaded now by hand,
try it but I believe you need the maven-met
[ http://jira.codehaus.org/browse/MEV-274?page=all ]
Carlos Sanchez closed MEV-274:
--
Assign To: Carlos Sanchez
Resolution: Cannot Reproduce
Without more details I have no idea what's the problem
> xml-api package in common-digester's pom file
> -
[ http://jira.codehaus.org/browse/MEV-274?page=all ]
Carlos Sanchez moved MNG-1909 to MEV-274:
-
Priority: (was: Minor)
Group ID: commons-digester
Version: (was: 2.0)
Artifact ID: commons-digester
Component:
[ http://jira.codehaus.org/browse/MEV-272?page=comments#action_54681 ]
Carlos Sanchez commented on MEV-272:
copied the jar, could you create a relocation?
About surefire, the problem is in the repocleaner, this pom is converted from m1
> Groovy 1.0-jsr-
Create a java source code artifact handler
--
Key: MAVEN-1736
URL: http://jira.codehaus.org/browse/MAVEN-1736
Project: Maven
Type: New Feature
Components: model
Versions: 1.1-beta-2
Reporter: Stephane Nicoll
A
[ http://jira.codehaus.org/browse/MNG-1910?page=all ]
Jochen Wiedmann updated MNG-1910:
-
Attachment: jdk_plus.patch
> Allow jdk 1.4+ as profile requirement
> -
>
> Key: MNG-1910
> URL: http://jira.cod
On 1/2/06, Milos Kleint <[EMAIL PROTECTED]> wrote:
> since you do the work, you pick. :)
> Just let me know then, I'll update the mevenide support then.
Issue created: http://jira.codehaus.org/browse/MAVEN-1736
Regards,
Stéphane
--
.::You're welcome ::.
On 1/2/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> On 1/2/06, Milos Kleint <[EMAIL PROTECTED]> wrote:
> > Ok, now with M2 in the picture it seems to make some sense. However
> it's
> > unfortunate that we won't be able to use the artifact taglib for
> uploading
> > the artifacts. (if I unde
On 1/2/06, Milos Kleint <[EMAIL PROTECTED]> wrote:
> Ok, now with M2 in the picture it seems to make some sense. However it's
> unfortunate that we won't be able to use the artifact taglib for uploading
> the artifacts. (if I understood Arnaud correctly in his reply)
We just need to implement an
On 1/2/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> Milos,
>
> Not a single clue about it. The only reason I see is explained in the
> eclipse plugin changes:
>
>
> Java source location now defaults to
> MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar
> (standard locat
Allow jdk 1.4+ as profile requirement
-
Key: MNG-1910
URL: http://jira.codehaus.org/browse/MNG-1910
Project: Maven 2
Type: Improvement
Components: POM
Versions: 2.0.1
Reporter: Jochen Wiedmann
Attachments: jdk_plu
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060102.134500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060102.134500.txt
-
To unsubscribe, e-mai
I think it was done like this to use the artifact taglib (which by default
deploys the artifact in //-.).
It could be possible to change it with a custom ArtifactTypeHandler (as done
in the ejb plugin for example) but nobody asked me to do it. I'm not sure
that this goal is often used.
Arnaud
On
1 - 100 of 141 matches
Mail list logo
