Re: Fixes and changes for maven 1.0

[Andy Jefferson]

On Thu, 2003-07-31 at 06:50, [EMAIL PROTECTED] wrote:
> If you have a fix or a change you would like to be in maven 1.0, please 
> ensure that:
> 
> 1) It's in Jira ( 
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030 )
> 2) it's in the roadmap ( 
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&report=roadmap
> )
> 
> If it's not, it wont be looked at for the release.

Not sure how I get things into the roadmap but I have them all in JIRA.
The issues I'd like in a 1.0 are

MAVEN-587 - Changes plugin extension : I included a patch for doing this
MAVEN-575 - Plugin loading bug
MAVEN-583 - WAR file naming : ESSENTIAL !
MAVEN-592 - Bug in XRef/Multiproject naming hyperlinks


Thx :-)
-- 
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Fixes and changes for maven 1.0

[Simon Matic Langford]

How do I get something into the roadmap?

simon

The information contained in this e-mail is intended only for the person
or
entity to which it is addressed and may contain confidential and/or
privileged material. If You are not the intended recipient of this
e-mail,
the use of this information or any disclosure, copying or distribution
is
Prohibited and may be unlawful. If you received this in error, please
contact the sender and delete the material from any computer. The views
expressed in this e-mail may not necessarily be the views of The PCMS
Group
plc and should not be taken as authority to carry out any instruction
contained.
 

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: 31 July 2003 06:51
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Fixes and changes for maven 1.0
> 
> 
> If you have a fix or a change you would like to be in maven 
> 1.0, please 
> ensure that:
> 
> 1) It's in Jira ( 
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030 )
> 2) it's in the roadmap ( 
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&re
port=roadmap 
)

If it's not, it wont be looked at for the release.

There are a whole heap of bugs listed as unscheduled at:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
&pid=10030&sorter/order=ASC&sorter/field=priority&resolutionIds=-1&fixfo
r=-1

These WILL NOT be fixed for Maven 1.0. If you've raised issues and
they're 
unscheduled, NOW  is the time to get them in a release.
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Regarding Maven 10

[S. Radhakrishnan]

Hi,

can you tell me about the advantages of maven 10
or suggest me any link to view the same??

I am planning to move from Maven 9 to Maven 10.. for that I need to document
the features..


Regards,
Radhakrishnan.

-Original Message-
From: Ben Walding [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:28 AM
To: Maven Users List
Subject: Re: Regarding google search


Thanks Tim.

Added to http://wiki.codehaus.org/maven/XdocDocumentation

Tim Anderson wrote:

>Add a  element to your navigation.xml file. E.g:
>
>
>  
>
>   ..
>
>
>
>  ...
>
>-Tim
>
>
>
>>-Original Message-
>>From: S. Radhakrishnan [mailto:[EMAIL PROTECTED]
>>Sent: Monday, 21 July 2003 3:32 PM
>>To: 'Maven Users List'
>>Subject: Regarding google search
>>
>>
>>Hi...
>>
>>How to enable google search using Maven???
>>
>>Regards,
>>RK.
>>
>>-
>>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]

Fixes and changes for maven 1.0

[dion]

If you have a fix or a change you would like to be in maven 1.0, please 
ensure that:

1) It's in Jira ( 
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030 )
2) it's in the roadmap ( 
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&report=roadmap 
)

If it's not, it wont be looked at for the release.

There are a whole heap of bugs listed as unscheduled at:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10030&sorter/order=ASC&sorter/field=priority&resolutionIds=-1&fixfor=-1

These WILL NOT be fixed for Maven 1.0. If you've raised issues and they're 
unscheduled, NOW  is the time to get them in a release.
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/

Re: cvs snapshot

[dion]

$)CCVS HEAD is currently unusable for most people.
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/


[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on 31/07/2003 04:56:19 AM:

> Hi,
> 
> I checked out maven cvs snapshot. 
> It was successful to build maven.
> But there was an abnormal output
> when I execute 'maven -g' at the maven module directory
> Available [Plugins] / Goals
> ```
> I test 'maven site' at the same directory, and I got errors as follows
> 
> site:
> 
> site:
> [EMAIL PROTECTED]  &site:
> 
> [EMAIL PROTECTED]  &site:
> word2html:generate:
> 
> xdoc:init:
> 
> xdoc:init:
> [mkdir] Created dir:
> C:\Workbench\Dev\OpenSource\cvs.apache.org\maven\target\generated-xdocs
> 
> BUILD FAILED
> com.werken.werkz.UnattainableGoalException: Unable to obtain goal
> [EMAIL PROTECTED]&site] -- null:49:46:  java.lang
> .NullPointerException
> at com.werken.werkz.Goal.fire(Goal.java:649)
> at com.werken.werkz.Goal.attain(Goal.java:580)
> at com.werken.werkz.Goal.attainPreGoals(Goal.java:687)
> at com.werken.werkz.Goal.fire(Goal.java:624)
> at com.werken.werkz.Goal.attain(Goal.java:580)
> at
> 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:493)
> at org.apache.maven.Maven.attainGoals(Maven.java:253)
> at org.apache.maven.cli.App.doMain(App.java:451)
> at org.apache.maven.cli.App.main(App.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> at
> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:543)
> at com.werken.forehead.Forehead.main(Forehead.java:573)
> org.apache.commons.jelly.JellyTagException: null:49:46: 
> java.lang.NullPointerException
> at
> 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:683)
> at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:288)
> at
> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at
> org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
> at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88)
> at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at
> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at
> 
org.apache.maven.jelly.tags.werkz.MavenAbstractWerkzTag.runBodyTag(MavenAbst
> ractWerkzTag.java:94)
> at
> 
org.apache.maven.jelly.tags.werkz.MavenAbstractGoalTag$MavenGoalAction.perfo
> rmAction(MavenAbstractGoalTag.jav
> a:127)
> at com.werken.werkz.Goal.fire(Goal.java:644)
> at com.werken.werkz.Goal.attain(Goal.java:580)
> at com.werken.werkz.Goal.attainPreGoals(Goal.java:687)
> at com.werken.werkz.Goal.fire(Goal.java:624)
> at com.werken.werkz.Goal.attain(Goal.java:580)
> at
> 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:493)
> at org.apache.maven.Maven.attainGoals(Maven.java:253)
> at org.apache.maven.cli.App.doMain(App.java:451)
> at org.apache.maven.cli.App.main(App.java:1015)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> at
> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:543)
> at com.werken.forehead.Forehead.main(Forehead.java:573)
> Caused by: java.lang.NullPointerException
> at
> 
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
> :545)
> at
> 
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
> :533)
> at
> 
org.apache.maven.jelly.tags.werkz.MavenAttainGoalListener.preAttain(MavenAtt
> ainGoalListener.java:134)
> at com.werken.werkz.Goal.attain(Goal.java:575)
> at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
> at com.werken.werkz.Goal.attain(Goal.java:578)
> at
> 
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTa
> g.java:79)
> at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> ... 22 more
> Root cause
> java.lang.NullPointerException
> at
> 
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
> :545)
> at
> 
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
> :533)
> at
> 
org.apache.maven

RE: Using Ant and Maven

[Brett Porter]

You can - do a maven.xml:
 

  

  

 
However, if you decide to go to maven, you should move your common ant stuff
into a custom plugin and share it across your projects - that's what we did
:)
 
Cheers,
Brett

-Original Message-
From: Mike Dougherty [mailto:[EMAIL PROTECTED] 
Sent: Thursday, 31 July 2003 9:58 AM
To: Maven Users
Subject: Using Ant and Maven


I've got all of about 2 hours experience with Maven. So far it's looking
pretty good. It seems to be purposed toward an OSS project, but I think we
will still be able to use it for internal projects. I've been able to
generate a simple site with Javadocs, a CheckStyle report, and some other
stuff.

Anyway, we have a lot of time and effort into our pretty sophisticated ant
build files. Is there a way I can use both? Can I call out to my ant
build.xml from within the project.xml? If so, how?

I don't think I am going to be able to convince the powers that be to just
drop Ant and re-do everything with Maven. If they are going to buy off on
using Maven it's going to have to work in conjunction with Ant for some time
to come. I did notice a section in the "Ant Guide" that will be devoted to
this purpose, but the information isn't there yet.

Thanks,
Mike




-- 

Mike Dougherty

Sr. Software Engineer   | [EMAIL PROTECTED] 

XIFIN, Inc. |   http://www.xifin.com

Ph: 858.793.5700| Fax: 858.793.5701

Fingerprint: 29DE DC92 822E B6F0 6A66  BCB8 8FE2 C562 7FB2 B342

Using Ant and Maven

[Mike Dougherty]

I've got all of about 2 hours experience with Maven. So far it's looking pretty good. It seems to be purposed toward an OSS project, but I think we will still be able to use it for internal projects. I've been able to generate a simple site with Javadocs, a CheckStyle report, and some other stuff.

Anyway, we have a lot of time and effort into our pretty sophisticated ant build files. Is there a way I can use both? Can I call out to my ant build.xml from within the project.xml? If so, how?

I don't think I am going to be able to convince the powers that be to just drop Ant and re-do everything with Maven. If they are going to buy off on using Maven it's going to have to work in conjunction with Ant for some time to come. I did notice a section in the "Ant Guide" that will be devoted to this purpose, but the information isn't there yet.

Thanks,
Mike




-- 
Mike Dougherty
Sr. Software Engineer   | [EMAIL PROTECTED] 
XIFIN, Inc. | http://www.xifin.com
Ph: 858.793.5700    | Fax: 858.793.5701
Fingerprint: 29DE DC92 822E B6F0 6A66  BCB8 8FE2 C562 7FB2 B342








signature.asc
Description: This is a digitally signed message part

Re: jar to use shortDescription for Specification-Title ?

[Paul Libbrecht]

Michal Maczka wrote:
Short description should be exactly one line long. 

For writing essays better use description tag...


Good to know... where can I read this ? Is it not specifiable in the 
schema ?

Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: jar to use shortDescription for Specification-Title ?

[Michal Maczka]

Short description should be exactly one line long. 

For writing essays better use description tag...

Michal

> -Original Message-
> From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 31, 2003 12:48 AM
> To: Maven User List
> Subject: jar:jar to use shortDescription for Specification-Title ?
> 
> 
> 
> Hi,
> 
> Apologize if someone mentionned this already earlier.
> 
> I got surprised today that my jar (in b10) came out with an invalid 
> manifest... the trouble was that my project.xml's description element 
> was multiline...
> Clearly, ant should still support multiline manifest attributes (and 
> reformat them probably)...
> 
> In the meantime, though, I found more sensible to use:
>  
> instead of
> value="${pom.shortDescription}"/>
> (at line 54 of maven-jar-plugin-1.0/plugin.jelly)
> 
> Aside of the fact that it removes my bug, does it not make more sense to 
> use the name of the project for a title than the short-description ?
> 
> Thanks.
> 
> Paul
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> --
> Polska lokalna w portalu INTERIA.PL >>> http://link.interia.pl/f1749
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

jar:jar to use shortDescription for Specification-Title ?

[Paul Libbrecht]

Hi,

Apologize if someone mentionned this already earlier.

I got surprised today that my jar (in b10) came out with an invalid 
manifest... the trouble was that my project.xml's description element 
was multiline...
Clearly, ant should still support multiline manifest attributes (and 
reformat them probably)...

In the meantime, though, I found more sensible to use:

instead of

(at line 54 of maven-jar-plugin-1.0/plugin.jelly)
Aside of the fact that it removes my bug, does it not make more sense to 
use the name of the project for a title than the short-description ?

Thanks.

Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: master property file

[James Macgill]

At 10:23 AM 7/24/2003 +0200, you wrote:
Dominik Dahlem wrote:

> This master project property file can be kept in source
> control and provides a single location for settings shared
> among sub-projects. Imagine you have 50 sub-projects and each
> of them contains a project properties file with settings
> which could well be shared. It's maintenance hell, if properties
> are likely to change.
I am in this very situation, I've found that in some cases I can use 
preGoals as a hack to work round this.  It's not elegant, but until 
property inheritance is in place it may help.

For example, I added this to the master maven.xml file and it seems to work.

preGoal in root maven.xml is fudging checkstyle to use 
geotools config settings



The echo is only there to remind me to take it out once the issue is resolved.

James

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs snapshot

[최인호]

Hi,
 
I checked out maven cvs snapshot. 
It was successful to build maven.
But there was an abnormal output
when I execute 'maven -g' at the maven module directory
Available [Plugins] / Goals
```
I test 'maven site' at the same directory, and I got errors as follows
 
site:
 
site:
[EMAIL PROTECTED]  &site:
 
[EMAIL PROTECTED]  &site:
word2html:generate:
 
xdoc:init:
 
xdoc:init:
[mkdir] Created dir:
C:\Workbench\Dev\OpenSource\cvs.apache.org\maven\target\generated-xdocs
 
BUILD FAILED
com.werken.werkz.UnattainableGoalException: Unable to obtain goal
[EMAIL PROTECTED]&site] -- null:49:46:  java.lang
.NullPointerException
at com.werken.werkz.Goal.fire(Goal.java:649)
at com.werken.werkz.Goal.attain(Goal.java:580)
at com.werken.werkz.Goal.attainPreGoals(Goal.java:687)
at com.werken.werkz.Goal.fire(Goal.java:624)
at com.werken.werkz.Goal.attain(Goal.java:580)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:493)
at org.apache.maven.Maven.attainGoals(Maven.java:253)
at org.apache.maven.cli.App.doMain(App.java:451)
at org.apache.maven.cli.App.main(App.java:1015)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
org.apache.commons.jelly.JellyTagException: null:49:46: 
java.lang.NullPointerException
at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:683)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:288)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.maven.jelly.tags.werkz.MavenAbstractWerkzTag.runBodyTag(MavenAbst
ractWerkzTag.java:94)
at
org.apache.maven.jelly.tags.werkz.MavenAbstractGoalTag$MavenGoalAction.perfo
rmAction(MavenAbstractGoalTag.jav
a:127)
at com.werken.werkz.Goal.fire(Goal.java:644)
at com.werken.werkz.Goal.attain(Goal.java:580)
at com.werken.werkz.Goal.attainPreGoals(Goal.java:687)
at com.werken.werkz.Goal.fire(Goal.java:624)
at com.werken.werkz.Goal.attain(Goal.java:580)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:493)
at org.apache.maven.Maven.attainGoals(Maven.java:253)
at org.apache.maven.cli.App.doMain(App.java:451)
at org.apache.maven.cli.App.main(App.java:1015)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
:545)
at
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
:533)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalListener.preAttain(MavenAtt
ainGoalListener.java:134)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:578)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTa
g.java:79)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
... 22 more
Root cause
java.lang.NullPointerException
at
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
:545)
at
org.apache.maven.plugin.PluginManager.createPluginContext(PluginManager.java
:533)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalListener.preAttain(MavenAtt
ainGoalListener.java:134)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:578)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTa
g.java:79)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at
org.apache.

RE: Two requests

[Michal Maczka]

> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 30, 2003 6:42 PM
> To: Maven Users List
> Subject: Re: Two requests
>
>
> Joshua Spiewak wrote:
>
> > I was wondering if the latest Jakarta Taglibs standard/jstl jars
> > (version 1.0.3) could be uploaded to ibiblio.
>
> The procedure of upload requests is described in Maven docs, can't
> remember where though. Try you luck with site search.
>
> > Also, is there any plan for site:deploy to be able to use ftp?  My web
> > host company does not give me shell access, so I will either
> need to ftp
> > by hand, or if no one is currently working on ftp perhaps I can
> take it up.
>
> FTP and few other deployment methods are implemented in the 'artifact'
> plugin. Plugging them into 'jar' and site 'plugins' should be really
> straightforward task, but Michal (the author of artifact plugin) decided
> (or was told to) to wait until the deployers get some amount of testing
> through war/ear plugins.


There is one more issue to which I want to resolve before I would  use this
plugin for deploying sites:
I want to make smarter SCP deployer which after receiving a list of files to
deploy will :

a) create a zip file (locally)
b) deploy
c) unzip (remotely)

This can be completely transparent (internally hidden in SCP/SSH deployer)
but will result is huge improvement of performance (usual instead of coping
MB it will just copy KB)
This is pretty much the same what site:deploy goal does .

This should be rather simple to implement (hope to this during weekend)

But surly this will be supported only by SCP deployer.



>I don't know how long are these tests about
> to last. AFAICT no problems with war/ear deployments were reported
> lately - either because they work perfecly, or nobody uses them.
>

could be second option :)


What I really need to finish artifact plugin are Windows/(Li/U)nix scripts.

I want to have scripts which

a) open SSH tunnel/session (1st script)
b) start maven session which will deploy
c) maven will deploy using SSH session open in step a) (2nd script)

So authentication is done completely outside maven ( I have class which I
call External Deployer for that)

This is needed by those who don't want to compromise their security by
keeping passwords
in open text
(forget please about the fact that FTP/HTTP/PROXY authentication is not
secure at all)


If somebody ___HAS__ such scripts I will have more time to read books
during weekends
(so maybe I will be a bit smarter...)

I had very many ideas how to make it simple and secure but non of them was
any good
I doubt if such solution exists. E.g. I was thinking about something like
password store
which will be similar to java key store but will keep all the passwords
which maven might need.
This store will be protected by one password (maybe even by session
passwords like in banks? :) )


But back to reality ... the key requirement for me is to  make this process
a) secure
b) automated ( no human interaction is needed so e.g. continuous integration
system can do the work)

At the moment I fail to see a possibility of implementing it without using
long-living processes or external security infrastructure.

Michal



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Two requests

[Rafal Krzewski]

Joshua Spiewak wrote:

I was wondering if the latest Jakarta Taglibs standard/jstl jars 
(version 1.0.3) could be uploaded to ibiblio.
The procedure of upload requests is described in Maven docs, can't
remember where though. Try you luck with site search.
Also, is there any plan for site:deploy to be able to use ftp?  My web 
host company does not give me shell access, so I will either need to ftp 
by hand, or if no one is currently working on ftp perhaps I can take it up.
FTP and few other deployment methods are imlemented in the 'artifact' 
plugin. Plugging them into 'jar' and site 'plugins' should be really 
straightforward task, but Michal (the author of artifact plugin) decided
(or was told to) to wait until the deployers get some amount of testing
through war/ear plugins. I don't know how long are these tests about
to last. AFAICT no problems with war/ear deployments were reported
lately - either because they work perfecly, or nobody uses them.

R.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Two requests

[Joshua Spiewak]

Hello again,

I was wondering if the latest Jakarta Taglibs standard/jstl jars (version 
1.0.3) could be uploaded to ibiblio.
Also, is there any plan for site:deploy to be able to use ftp?  My web host 
company does not give me shell access, so I will either need to ftp by 
hand, or if no one is currently working on ftp perhaps I can take it up.

			-- Josh

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: plugins not unpacking in my local repository

[Daniel . B . Brown]

Yes, I am using b10?  I'll remember to add carriage returns next time.

-Original Message-
From: Ben Walding [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 9:55 AM
To: Maven Users List
Subject: Re: plugins not unpacking in my local repository


Have a look at http://wiki.codehaus.org/maven/MigratingFromBeta9ToBeta10

Consider the use of the return key to break up your emails, as that is 
just a crime against paragraphs! :P

Are you using b10?


[EMAIL PROTECTED] wrote:

>I created a local plugin that sets up our developer's local environment
>(sets build.properties files and creates the maven.local.repo directory in
a
>standard location) in order to get developers working under maven in a
quick
>and easy fashion.  I successfully installed and deployed it using
>plugin:install and plugin:deploy respectively.  The plugin works similar to
>the genapp plugin in that it copies a standard build.properties file
located
>in the plugin to the user's home directory.  All this works as expected.
>The next test was to remove my build.properties file and the
>maven.local.repo directory to simulate a complete new install of maven with
>the addition of my plugin.  Unfortunately, when I invoke my goal that
>initializes my environment, the build fails when it tries to copy the
>plugin's copy of the build.properties file to my home directory because the
>directory this file resides does not exist.  i.e. maven did not
>automatically unpack the plugin in the ${maven.local.repo}/plugins
>directory.  This might be a bug, I don't know.  Is there a way to force
>maven to unpack the plugin  or is it the ultimate responsibility of the
>plugin to unpack itself?  Any help would be appreciated.
>
>Thanks,
>
>- Dan
>
>
>-
>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: plugins not unpacking in my local repository

[Ben Walding]

Have a look at http://wiki.codehaus.org/maven/MigratingFromBeta9ToBeta10

Consider the use of the return key to break up your emails, as that is 
just a crime against paragraphs! :P

Are you using b10?

[EMAIL PROTECTED] wrote:

I created a local plugin that sets up our developer's local environment
(sets build.properties files and creates the maven.local.repo directory in a
standard location) in order to get developers working under maven in a quick
and easy fashion.  I successfully installed and deployed it using
plugin:install and plugin:deploy respectively.  The plugin works similar to
the genapp plugin in that it copies a standard build.properties file located
in the plugin to the user's home directory.  All this works as expected.
The next test was to remove my build.properties file and the
maven.local.repo directory to simulate a complete new install of maven with
the addition of my plugin.  Unfortunately, when I invoke my goal that
initializes my environment, the build fails when it tries to copy the
plugin's copy of the build.properties file to my home directory because the
directory this file resides does not exist.  i.e. maven did not
automatically unpack the plugin in the ${maven.local.repo}/plugins
directory.  This might be a bug, I don't know.  Is there a way to force
maven to unpack the plugin  or is it the ultimate responsibility of the
plugin to unpack itself?  Any help would be appreciated.
Thanks,

- Dan

-
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]

plugins not unpacking in my local repository

[Daniel . B . Brown]

I created a local plugin that sets up our developer's local environment
(sets build.properties files and creates the maven.local.repo directory in a
standard location) in order to get developers working under maven in a quick
and easy fashion.  I successfully installed and deployed it using
plugin:install and plugin:deploy respectively.  The plugin works similar to
the genapp plugin in that it copies a standard build.properties file located
in the plugin to the user's home directory.  All this works as expected.
The next test was to remove my build.properties file and the
maven.local.repo directory to simulate a complete new install of maven with
the addition of my plugin.  Unfortunately, when I invoke my goal that
initializes my environment, the build fails when it tries to copy the
plugin's copy of the build.properties file to my home directory because the
directory this file resides does not exist.  i.e. maven did not
automatically unpack the plugin in the ${maven.local.repo}/plugins
directory.  This might be a bug, I don't know.  Is there a way to force
maven to unpack the plugin  or is it the ultimate responsibility of the
plugin to unpack itself?  Any help would be appreciated.

Thanks,

- Dan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JGraph 2.2.1 upload to ibiblio

[Ben Walding]

FYI: Just uploaded JGraph 2.2.1 jars to ibiblio.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Help Needed .. InvalidJarIndexException

[Keld Mikkelsen]

Hi,

Are you by any chance behind a firewall? If so check the logfiles on your
firewall server for errors.

This is from the Maven User Guide:



   If you do require a proxy, the most appropriate place to set these   
   values would be in your ${user.home}/build.properties file.  


   ## --
   ## ${user.home}/build.properties 
   ## --
   .
   .
   maven.proxy.host = my.proxyserver.com
   maven.proxy.port = 8080  
   maven.proxy.username = username  
   maven.proxy.password = password  
   .
   .





/Keld Mikkelsen





|-+-->
| |"Shelly_Singh"|
| |<[EMAIL PROTECTED]|
| |sys.com>  |
| |30-07-2003 07:06  |
| |Please respond to |
| |"Maven Users List"|
| |  |
| |  |
|-+-->
  
>--|
  |
  |
  |To:  "Maven Users List" <[EMAIL PROTECTED]> 
 |
  |cc:  (bcc: Keld Mikkelsen/IT/DK_GBJ/Grundfos)   
  |
  | Subject:  Help Needed .. InvalidJarIndexException  
  |
  
>--|




Hi,

I am very new to maven.
I installed maven and called genapp. I get the InvalidJarIndexException.
I also tried running maven for an existing application by creating a
project.xml. I still get the same exception.

Please help.

Regards,
Shelly

sun.misc.InvalidJarIndexException: Invalid index!
at
sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:594)
at sun.misc.URLClassPath.getResource(URLClassPath.java:134)
at java.net.URLClassLoader$2.run(URLClassLoader.java:349)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:346)
at java.lang.ClassLoader.getResource(ClassLoader.java:734)
at java.lang.Class.getResource(Class.java:1249)
at
org.apache.commons.betwixt.XMLIntrospector.findByXMLDescriptor(XMLInt
rospector.java:531)
at
org.apache.commons.betwixt.XMLIntrospector.introspect(XMLIntrospector
.java:256)
at
org.apache.commons.betwixt.io.BeanReader.registerBeanClass(BeanReader
.java:143)
at
org.apache.maven.MavenUtils.createBeanReader(MavenUtils.java:560)
at
org.apache.maven.MavenUtils.getProjectBeanReader(MavenUtils.java:324)

at org.apache.maven.MavenUtils.getProject(MavenUtils.java:198)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:160)
at
org.apache.maven.MavenSession.initializeRootProject(MavenSession.java
:324)
at org.apache.maven.MavenSession.initialize(MavenSession.java:234)
at org.apache.maven.cli.App.doMain(App.java:514)
at org.apache.maven.cli.App.main(App.java:1088)
at java.lang.reflect.Method.invoke(Native Method)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time:  2 seconds




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTEC