The following comment has been added to this issue:
Author: Marcel May
Created: Fri, 20 Aug 2004 2:11 AM
Body:
It is severe as it is a security risk and got me ssh locked out of
the site server (not nice when you do not sit beside the machine).
It is not a major issue if consideri
The following comment has been added to this issue:
Author: bmak
Created: Thu, 19 Aug 2004 10:59 PM
Body:
RE: the suggestion about the genapp template
so your suggestion would have been perfect if the template option included some
support for multiprojects, including letting the
The following comment has been added to this issue:
Author: bmak
Created: Thu, 19 Aug 2004 10:51 PM
Body:
http://www.google.com/search?hl=en&ie=UTF-8&q=CreatingJ2eeApplications+&btnG=Google+Search
-
View this comme
On Thursday 19 August 2004 18:35, Tobias Wolf wrote:
> In an first approach I simply created the directory 'template' and 'jars'
> under my .magic/main and defined it as an ressource in my index.xml. When i
> can append it to the dependencies of my project and i am finished. Now I am
> able to use
Per Brett's suggestion, I'm moving this discussion from Ant's dev list
(see http://tinyurl.com/6rcxr for the precending conversation) to here.
Summary: I'd like to write an Ant task for accessing POMs in
conjunction with the JAM project ( http://javagen.sf.net/ ). Originally
I was just looking at
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Thu, 19 Aug 2004 5:39 PM
Body:
try
maven genapp
use template ejb/web/struts/struts-jstl/web-jstl
then type in
maven ear (for ejb) // I think, I forgot if this worked or not
or
maven war (for
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 19 Aug 2004 4:23 PM
Body:
Happened to me also some weeks ago and lately to my collegue. IHMO "major" does not
classify this issue.
-
The following issue has been updated:
Updater: Adam Fisk (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 3:43 PM
Comment:
This one correct the issue number in changes.xml -- the previous one was wrong.
Changes:
Attachment changed to jasper-version-patch.txt
--
The following issue has been updated:
Updater: Adam Fisk (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 3:31 PM
Comment:
Here's the update to 4.1.30 versions of the Jasper compiler and runtime. These are
the same versions shipped with the latest Jetty releases.
Changes:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJETTY-4
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Adam Fisk
Created: Thu, 19 Aug 2004 3:26 PM
Body:
It's working fine for me with the older versions of jasper, but the Jetty folks
include the 4.1.30 Jasper versions with their downloads, so it's probably a good idea
to u
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSITE-13
Here is an overview of the issue:
-
Key:
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Thu, 19 Aug 2004 11:56 AM
Applied. Are you sure you don't need to upgrade the jasper versions? I hope your have
tested your changed? :-) Next time, could you please also attach the patch for
changes.xml?
vmassol 2004/08/19 08:52:15
Modified:jetty/xdocs changes.xml
jettyproject.xml
Log:
Upgraded dependency to Jetty 4.2.20.
Revision ChangesPath
1.7 +3 -0 maven-plugins/jetty/xdocs/changes.xml
Index: changes.xml
===
The following issue has been updated:
Updater: Adam Fisk (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 11:46 AM
Comment:
Here's the little patch to use the latest Jetty posted at ibiblio. They don't have
4.2.21, but this is good enough.
Thanks Vincent.
-Adam
Changes:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-190
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJETTY-3
Here is an overview of the issue:
-
Key:
The following issue has been updated:
Updater: Alexandre Vivien (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 10:19 AM
Comment:
Patch for the plugin.properties file.
Changes:
Attachment changed to plugin.properties.patch
-
The following issue has been updated:
Updater: Alexandre Vivien (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 10:20 AM
Comment:
Patch for the properties.xml file
Changes:
Attachment changed to properties.xml.patch
The following issue has been updated:
Updater: Alexandre Vivien (mailto:[EMAIL PROTECTED])
Date: Thu, 19 Aug 2004 10:18 AM
Comment:
Patch for the cruisecontrol.jsl file
Changes:
Attachment changed to cruisecontrol.jsl.patch
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCRUISECONTROL-12
Here is an overview of the issue:
-
carlos 2004/08/19 03:53:52
Modified:artifact/xdocs properties.xml
Log:
Documented use of maven.repo.x.port with scpexe
Revision ChangesPath
1.10 +7 -0 maven-plugins/artifact/xdocs/properties.xml
Index: properties.xml
=
carlos 2004/08/19 03:49:33
Modified:artifact/xdocs examples.xml
Log:
Rolled back to 1.6
Revision ChangesPath
1.8 +1 -0 maven-plugins/artifact/xdocs/examples.xml
Index: examples.xml
===
RC
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Thu, 19 Aug 2004 6:46 AM
Body:
Ok, I was wrong and it exists but it's not documented. As Joerg stated with scpexe you
should use the args property
--
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Thu, 19 Aug 2004 6:39 AM
maven.repo.[name].port property just doesn't exist
-
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Thu, 19 Aug 2004 6:37 AM
Body:
That's general info about it but nothing about maven.repo.[name].port property
-
View this comment:
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 19 Aug 2004 6:36 AM
Body:
IMHO the port property just makes no sense for scpexe, since you cannot know what
option is used. For the internal handled protocols this should not be the problem.
-
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 19 Aug 2004 6:33 AM
Body:
http://maven.apache.org/reference/plugins/artifact/protocols.html
Just next point in navigation :)
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Thu, 19 Aug 2004 6:29 AM
Body:
Thanks Joerg for enlighten me. I've changed my mind and removed the port property from
the sample in documentation, but,
where have any of you seen documented that p
carlos 2004/08/19 03:18:25
Modified:artifact/xdocs examples.xml
Log:
Removed port property from a sample
Revision ChangesPath
1.7 +0 -1 maven-plugins/artifact/xdocs/examples.xml
Index: examples.xml
===
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-28
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 19 Aug 2004 6:12 AM
Body:
Maybe it would be easier to document, that the m.r.x.port property is not supported
for scpexe:// and the user can add the necessary params to the m.r.x.s.arg paramet
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-28
Here is an overview of the issue:
-
Key: M
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-27
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: Martin Jaeger
Created: Thu, 19 Aug 2004 3:29 AM
Body:
The given bugfix works perfect for me.
Please include in the next official release.
Thanks
-
View th
35 matches
Mail list logo
