2007/9/6, Ted Husted [EMAIL PROTECTED]:
I just wanted to try a dry-run on 2.1.x first, later tonight (after I
get some actual work done!).
Just to be complete: the release process won't work until all the snapshot
dependencies are resolved. In particular, there is a dependency to xwork
I'm nervous since there doesn't seem to be a way to try a dry run on
2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
apply the patch to the branch, we might as well try it there first.
-Ted.
On 9/7/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
2007/9/7, Ted Husted [EMAIL
On 9/7/07, Ted Husted [EMAIL PROTECTED] wrote:
I'm nervous since there doesn't seem to be a way to try a dry run on
2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
apply the patch to the branch, we might as well try it there first.
Jim pointed out the -DdryRun=true
2007/9/7, Wendy Smoak [EMAIL PROTECTED]:
And just in general, we use the release plugin at Maven, have used it
at MyFaces, and at work we use the release management feature in
Continuum (which is based on the same thing).
You forgot to mention Tiles :-)
Antonio
Sorry for the late reply to everyone. I've been super busy.
The project uses a build system called Vertigo-Ant to make it simpler to
download deps and such. It is something we use at Texturemedia and makes
this project simpler. I can point you to that project if you want to
build it.
As for
I tried building it from source, using 1.6, under Eclipse, and the
problem is that a dependency on net.java.lang.URLClassLoaderResolver
was introduced between .05 and .14 in the DefaultResultMapBuilder. I
In the build.xml and IntelliJ files there are a number of dependencies
on various products.
Okay, the ZIP file is out there and contains the JAR , source JAR and
Java.net Commons JAR. This should be deployable just via extraction. As
for the JDK 1.6, I'm working on reverting that now. Although I have to
say JAXB right in the JDK and unmarshalling with like 2 lines of code
will be
I'm using a few other things from that package.
You are probably right though - reducing dependencies to put it into
core is best. I'll work on moving those files over today.
What issues are you having? I could probably fix them pretty quickly.
I'll definitely get an example or two
The project Struts 2 SVN - Main Build has the following 1 change by 1 author:
*Don Brown* made the following changes at
Comment:
Turning off static method access in ognl expressions by default
WW-2160
Okay. Just finishing up the release of 0.18 and I'll put up that ZIP
file. This uses DOM (just to save myself the headache of SAX handlers)
and all the tests pass. I completely removed all the JDK 1.6 and JAXB
stuff and things should be fine with JDK 1.5.
You all should be able to drop the
Can you also post a WAR with the hello-world page. I'm still having
trouble getting it to run here.
I don't know if it would be part of rolling back or not, but it might
also be helpful to extract the URLClassLoaderResolver from the other
JAR, rather than pull the whole thing along for the sake
Sounds good. Thanks.
- Original Message
From: Don Brown [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org; Jon Wilmoth [EMAIL
PROTECTED]
Sent: Friday, September 7, 2007 9:20:36 AM
Subject: Re: [s2] Struts 2 and OGNL findings
Correct, static fields are still
Ah, good catch. I'll fix that so that if it isn't set, it will assume no
packages exist, which seems like it is an acceptable case.
-bp
Ted Husted wrote:
It wanted smarturls.action.packages to be set to something that
existed. An empty string also seems to work.
I was walking through the
Does #2 include access to static fields (i.e. Constants) or are these not
affected by your change?
Thanks,
Jon
- Original Message
From: Don Brown [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org
Sent: Friday, September 7, 2007 9:04:37 AM
Subject: [s2] Struts 2 and
I spent the last couple days looking into the OGNL situation in Struts
2 and XWork, with the intent on if not eliminating it, at least
blocking it cleanly off. The summary is this:
1. Refactored the TypeConverter system away from OGNL into new XWork API [1]
2. Turned off static method access in
The project Struts 2 SVN - Main Build has the following 1 change by 1 author:
*Don Brown* made the following changes at
Comment:
Fixing test WW-2160
/struts/struts2/trunk/core/src/main/java/org/apache/struts2/config/BeanSelectionProvider.java
(573609)
It wanted smarturls.action.packages to be set to something that
existed. An empty string also seems to work.
I was walking through the walk through, and so I hadn't created a
package folder before creating my first page.
It seems to be working now, so now I can play some more :)
-Ted.
On
Thanks so much, Don. OGNL has been a point of concern, and I'm glad
you were able to look into it.
With TP5 moving away from OGNL, do we know of any other projects other
than XW still using it?
If not, then if we (meaning XW) starts to tweak OGNL, would it make
sense to bring OGNL into the XW
It looks like the plugin requires Java 1.6; I have tried running it
under 1.6 yet, but that may be the issue.
On Sep 6, 2007, at 7:53 PM, Ted Husted wrote:
When deploying the SmartUrls plugin, my system is unable to find
the class
net.java.lang.URLClassLoaderResolver;
I tried to google
2007/9/7, Jim [EMAIL PROTECTED]:
Fortunately, you can do a dry run:
mvn release:prepare -DdryRun=true
After running the dry run, use this to cleanup:
mvn release:clean
See the heading Do a Dry Run for the Maven 2 release plugin
documentation:
Fortunately, you can do a dry run:
mvn release:prepare -DdryRun=true
After running the dry run, use this to cleanup:
mvn release:clean
See the heading Do a Dry Run for the Maven 2 release plugin
documentation:
http://maven.apache.org/plugins/maven-release-plugin/usage.html
On Sep 7,
2007/9/7, Ted Husted [EMAIL PROTECTED]:
Does step 2 Tag the release by using the release:prepare goal of
Maven: actually tag the release in SVN? (How does it know what symbol
to use?) Or is the word tag being used in another sense?
The sense is right :-) But the release:prepare goal does
22 matches
Mail list logo
