The discussion stemmed directly from the vote. I wanted to know why this
is being a separate product/distribution, and the answer was it could be
used for Struts 1.x ... but is that likely?
Paul
Ted Husted wrote:
On 1/24/07, Don Brown <[EMAIL PROTECTED]> wrote:
The struts annotations jar is
As discussed on this list, Struts 2 plugins can create their own tag
library, extending our own. Several folks are working on a table tag
plugin, for example. Musachy has been filing JIRA tickets that make the
struts annotations jar useful to plugins, which we've scheduled for
after 2.0.4.
On 1/24/07, Don Brown <[EMAIL PROTECTED]> wrote:
The struts annotations jar is currently only used in Struts 2 core, but
that doesn't have to be the case. In fact, we hope to use it in plugins
inside and outside the Struts project, and it is certainly applicable to
Struts 1 if it chose to use it
ions too? Do we share other artifacts under maven?
Are we sure we want a common maven folder?
Paul asked, and Don answered a few days ago:
http://www.nabble.com/-VOTE--Release-Struts-Annotations-1.0.0-t3084860.html#a8596388
--
Wendy
---
No, it's not causing problems yet. I'm able to build a clean assembly
from a checkout of the struts2 trunk in isolation. But I'm not clear
on why we even need a separate JAR and release series. Is Struts 1
using the annotations too? Do we share other artifacts under maven?
Are we sure we want a co
On 1/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 1/26/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Please also comment out any _snapshot_ repository or pluginRepository
> definitions before tagging 2.0.4. They are not necessary for a
> release build that doesn't have snapshot dependencies, a
On 1/26/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Please also comment out any _snapshot_ repository or pluginRepository
definitions before tagging 2.0.4. They are not necessary for a
release build that doesn't have snapshot dependencies, and leaving
them in causes problems in corporate environm
On 1/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
What about this in the root POM?
struts-annotations
../maven/struts-annotations
This stanza presumes that a folder below what we have been tagging is present.
I'm not sure
What about this in the root POM?
struts-annotations
../maven/struts-annotations
This stanza presumes that a folder below what we have been tagging is present.
-Ted.
---
On 1/27/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
At the risk of complicating things, isn't bad form, if nothing else, to cut
a release based on a transient repository location? One of the reasons to
use Maven is to have a reproducible build, and a release is the kind of
build which is more l
On 1/26/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
The release manager for Struts 2.0.4 will need to add a profile to
settings.xml so that Maven can find the struts-annotations jar:
[untested]
...
struts-annotations-101-staging
struts-an
That said, I'm not sure if I messed up something here :)
Since struts(2)-blank-archetype is for setting up struts based apps,
there is no need for providing LICENSE and NOTICE files.
struts2-blank-plugin contains these files, which is fine then.
- Rene
Rene Gielen schrieb:
> The annotations modu
The annotations module was setup from struts-archetype-blank, so I
wonder if we should to add LICENSE and NOTICE files to the archetype to
avoid such issues in future...
- Rene
Don Brown schrieb:
> I don't understand - all of the Struts jars are missing those files.
> The only place I see it add
On 1/26/07, Don Brown <[EMAIL PROTECTED]> wrote:
Arg!! So now we have to start this whole process again, pushing the
2.0.4 release off at least three more days? There has really got to be
a better way to handle these types of minor modifications. Since the
lack of these two files is the only re
On 1/26/07, Don Brown <[EMAIL PROTECTED]> wrote:
Arg!! So now we have to start this whole process again, pushing the
2.0.4 release off at least three more days? There has really got to be
a better way to handle these types of minor modifications. Since the
lack of these two files is the only r
Arg!! So now we have to start this whole process again, pushing the
2.0.4 release off at least three more days? There has really got to be
a better way to handle these types of minor modifications. Since the
lack of these two files is the only reason for a -1 vote in many days of
voting, let'
1.3.5 does, but 2.0.3 does not.
On 1/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 1/25/07, Don Brown <[EMAIL PROTECTED]> wrote:
> I don't understand - all of the Struts jars are missing those files.
> The only place I see it added is in the assembly tarballs.
LICENSE and NOTICE must be pre
On 1/25/07, Don Brown <[EMAIL PROTECTED]> wrote:
I don't understand - all of the Struts jars are missing those files.
The only place I see it added is in the assembly tarballs.
LICENSE and NOTICE must be present in every distribution. At one
time, that just meant the .zip/.tar.gz files, but n
I don't understand - all of the Struts jars are missing those files.
The only place I see it added is in the assembly tarballs.
Don
Wendy Smoak wrote:
On 1/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Struts Annotations 1.0.0 has been tagged and is available for testing
...
Once you have
On 1/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Struts Annotations 1.0.0 has been tagged and is available for testing
...
Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.
-1 -- The jar is missing LICENSE and NOTICE files.
+1 worked for me as well
Ditto. +1
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com
"The truth is that we learned from João forever to be out of tune."
-- Caetano Veloso
+1 worked for me as well
cheers,
Rainer
> Struts Annotations 1.0.0 has been tagged and is available for testing
> in the following Maven repository:
>
>
> http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/
>
> To test this build, temporarily add a repository
+1 Worked for me
Wendy Smoak wrote:
Struts Annotations 1.0.0 has been tagged and is available for testing
in the following Maven repository:
http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/
To test this build, temporarily add a repository to pom.xml or
It should also be fairly easy to determine which version is required by
a specific struts version by looking at the version declared in the pom.
David
Don Brown wrote:
The struts annotations jar is currently only used in Struts 2 core, but
that doesn't have to be the case. In fact, we hope to
+1, works as expected for me
Wendy Smoak schrieb:
> Struts Annotations 1.0.0 has been tagged and is available for testing
> in the following Maven repository:
>
>
> http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/
>
>
> To test this build, temporarily add
The struts annotations jar is currently only used in Struts 2 core, but
that doesn't have to be the case. In fact, we hope to use it in plugins
inside and outside the Struts project, and it is certainly applicable to
Struts 1 if it chose to use it. This is why it gets its own version
number a
Why isn't this considered version 2.0.3? We had a similar problem back
in 1.x when we tried to do the whole independent Struts packaging at
different version numbers. It was quickly apparent that there was no way
to easily know which package was compatible with another package.
Also I noticed
Worked great for me, +1
Don
Wendy Smoak wrote:
Struts Annotations 1.0.0 has been tagged and is available for testing
in the following Maven repository:
http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/
To test this build, temporarily add a repository t
Struts Annotations 1.0.0 has been tagged and is available for testing
in the following Maven repository:
http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/
To test this build, temporarily add a repository to pom.xml or
settings.xml, and change the struts-ann
29 matches
Mail list logo
