Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-507
Here is an overview of the issue:
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-506
Here is an overview of the issue:
--
Shouldn't the "maven.deploy." at least be a constant somewhere?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
[EMAIL PROTECTED] wrote on 19/06/2003 08:52:26 PM:
> michal 2003/06/19 03:52:25
>
> Modified:
"Michal Maczka" <[EMAIL PROTECTED]> wrote on 19/06/2003 10:48:48 PM:
> Please comment this:
>
>
> With new deployer API I am going to support deployment to many remote
> repositories.
> In reality many = 2 in most of the cases. But 2>1 ..
>
> I am proposing to use following properties:
>
> #th
BTW: Are you going to make jboss plugin compatible with jboss 3.2x
series?
What is not compatible? I seem to remember I have used it with JBoss
3.2.1.
maven.jboss.jmx.url.deploy=http://${maven.jboss.hostname}:${maven.jboss.
po
rt
}/jmx-
console/HtmlAdaptor?action=invo
jvanzyl 2003/06/19 16:26:22
Added: src/java/org/apache/maven DefaultProjectUnmarshaller.java
Log:
o New POM unmarshaller.
Revision ChangesPath
1.1 maven/src/java/org/apache/maven/DefaultProjectUnmarshaller.java
Index: DefaultProjectUnmarshaller.jav
jvanzyl 2003/06/19 16:26:08
Added: src/java/org/apache/maven DefaultProjectMarshaller.java
Log:
o New POM marshaller.
Revision ChangesPath
1.1 maven/src/java/org/apache/maven/DefaultProjectMarshaller.java
Index: DefaultProjectMarshaller.java
jvanzyl 2003/06/19 16:25:42
Modified:.project.xml
Log:
o Updating the deps for the new marshaller/unmarshaller for the POM. Hopefully
I can hand some stuff over to Ben :-)
Revision ChangesPath
1.279 +37 -7 maven/project.xml
Index: project.xml
==
Looks good. A few questions:
maven.repo.repo1.remote.group= goo
Is remote.group really needed? How is this different to pom.groupId?
maven.deploy.repo.ibiblio = http://www.ibiblio.org
maven.deploy.repo.ibiblio.directory = /maven
Is the extra deploy here a typo? If it is something different, what
michal 2003/06/19 15:02:37
Modified:src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers
FtpDeployer.java FileDeployer.java
src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtif
Wow you're very fast I just sent the mail an already got an answer :-))
I know that the source directories are configurable at the moment I
just wanted to make sure that this will also be the case in the future
(after eventually changes to the directory layout) because changing the
layout of a
On Thu, 19 Jun 2003, Juergen Heidak wrote:
>
> I like the idea of adding more structural information to the directory
> layout but all changes should be backward compatible because many
> projects already use maven and can not adapt a possible new structure
> without great effort.
>
> In oth
I like the idea of adding more structural information to the directory
layout but all changes should be backward compatible because many
projects already use maven and can not adapt a possible new structure
without great effort.
In other words: The path to the different source directories (jav
@@
cactus
cactus
- 13-1.5dev-20030607
+ 13-1.5dev-20030619
cactus
cactus-ant
- 13-1.5dev-20030607
+ 13-1.5dev-20030619
commons-httpclient
1.10 +7 -1 maven/src/plugins
jvanzyl 2003/06/19 07:53:26
Modified:xdocssun-licensing-journey.xml
Log:
o Sent a message off to Tom Kincaid for approval for the packages we collected
in this document.
Revision ChangesPath
1.11 +4 -0 maven/xdocs/sun-licensing-journey.xml
Index: su
That's my preference also. And it also makes it look like you can have
multiple build trees, yet not! Muahahaha... I demand more emails on the
user list dammit!
Michal Maczka wrote:
I also think it is bit inconsistent.
But think that the most consistent approach is
/ basedir
main
vmassol 2003/06/19 07:06:20
Modified:src/plugins-build/jboss plugin.jelly
src/plugins-build/jboss/xdocs changes.xml goals.xml
Log:
When generating the JBoss server configuration zip, exclude
JBoss tmp and log directories from the zip.
vmassol 2003/06/19 07:01:51
Modified:src/plugins-build/war plugin.jelly
Log:
fix comment
Revision ChangesPath
1.19 +11 -17maven/src/plugins-build/war/plugin.jelly
Index: plugin.jelly
===
RCS
The following issue has been updated:
Updater: Gareth Hunt (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Jun 2003 9:08 AM
Comment:
Have updated patch to reflect recent changes to the code.
Please ignore older patch file.
Changes:
Attachment changed from to plugin.jelly.pat
I also think it is bit inconsistent.
But think that the most consistent approach is
/ basedir
main
java
resources
aspects
conf
test
java
test-resources
...
Michal
P.S.
I am not saying we should change anything ...
> ---
On Thu, 2003-06-19 at 09:23, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 19 June 2003 15:02
> > To: Maven Developers List
> > Subject: Re: Why is the java source directory named "main" for
> plugins?
> >
> > On Thu, 2003-06-19 at
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 19 June 2003 15:02
> To: Maven Developers List
> Subject: Re: Why is the java source directory named "main" for
plugins?
>
> On Thu, 2003-06-19 at 06:32, Vincent Massol wrote:
> > Hi,
> >
> > Why is the java sou
On Thu, 2003-06-19 at 06:32, Vincent Massol wrote:
> Hi,
>
> Why is the java source directory named "main" for plugins (instead of
> "java")?
/src/test
/src/main
Seem to make more sense as a pattern as the testing code is also 'java'
code.
> Thanks
> -Vincent
>
>
> ---
On Thu, 2003-06-19 at 06:32, Vincent Massol wrote:
> Hi Michal,
>
> I've had a look at the source code for the new artifact plugin... and it
> is really proof-of-concept code at this stage and I'm totally sure there
> are lots of bugs (it is really far from production quality right now). I
> don't
Please comment this:
With new deployer API I am going to support deployment to many remote
repositories.
In reality many = 2 in most of the cases. But 2>1 ..
I am proposing to use following properties:
#the list of repositories. repo1, repo2 are aliases or nicknames of
repositories
maven.deploy
Thanks Michal. The war:install goal seems to be working for me now, so
I'll leave it as it is.
Thanks
-Vincent
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 19 June 2003 13:00
> To: Maven Developers List
> Subject: RE: new Artifact plugin and WAR plugin war:
With new deployer API I am going to support deployment to many remote
repsoitories.
In reality many = 2 in most of the cases. But 2>1 ..
I am proposiing to use follwoing properties:
#the list of repositories. repo1, repo2 are aliases or nicknames of
repositories
maven.repo.deploy = repo1, repo2
I quickly committed latest version which has install goal fixed.
Install snapshot should also work.
So I guess functionality is matching the old code.
But no problem fell free to use old install goal if you still have a
problems.
Michal
P.S
Note that war plugin haven't got deploy and deploy-sna
michal 2003/06/19 03:52:25
Modified:src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java
MavenDeployRequest.java
Log:
Install goal fixed
Revision ChangesPath
1.3 +22 -12
Hi,
Why is the java source directory named "main" for plugins (instead of
"java")?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Michal,
I've had a look at the source code for the new artifact plugin... and it
is really proof-of-concept code at this stage and I'm totally sure there
are lots of bugs (it is really far from production quality right now). I
don't mind that but I do mind using it in our WAR plugin at this poi
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 18 June 2003 22:01
> To: Maven Developers List
> Subject: RE: Recent changes in war plugin
[snip]
> > I think we're talking about the same thing. You can have a jelly
taglib
> > that wraps the Ant task.
> >
>
32 matches
Mail list logo
