On Aug 6, 2008, at 8:36 PM, Kevan Miller wrote:
On Aug 4, 2008, at 4:49 PM, Jacek Laskowski wrote:
On Mon, Aug 4, 2008 at 2:06 AM, Kevan Miller
[EMAIL PROTECTED] wrote:
B) A maven build will access multiple, redundant, versions of the
same
artifact. We control the versions that will be
Geronimo Revision: 683528 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080807/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080807
[INFO] BUILD
I have seen a number of problems with particularly new users running
Geronimo with GEP, and having problems. They switch to Java 5, and
things work for them. For GEP 2.1.2, which we want to get out ASAP
now that G2.1.2 is released, I think GEP should detect Java 6 when a
Geronimo server is
HI,
Trying to download the latest G V2.1.2 from my Eclipse workspace. These are
the steps I follow
1) Downloaded the latest GEP source.
2) Build was successful.
3) Started another instance of Eclipse from my Eclipse workspace.
4) Adding a server runtime.
5) Clicked on Download and Install.
6) Got
[
https://issues.apache.org/jira/browse/GERONIMO-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4228:
---
Patch Info: [Patch Available]
install plugin from deploy tool doesn't honor load=false
[
https://issues.apache.org/jira/browse/GERONIMO-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4228:
---
Fix Version/s: 2.1.3
Looks okay to me.
Fix also needs to go into the 2.1 branch.
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620615#action_12620615
]
Donald Woods commented on GERONIMODEVTOOLS-464:
---
This is also
We have danced around the problem of not being able to build Samples,
Plugins or GEP from a clean m2 repo without building the Server's
repository subdir for long enough. I believe it is time to create the
following location in SVN -
geronimo/repo
Which would hold our private patched
The 'Eclipse-LazyStart' header is deprecated, use 'Bundle-ActivationPolicy'
---
Key: GERONIMODEVTOOLS-465
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-465
Project:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620629#action_12620629
]
Ashish Jain commented on GERONIMODEVTOOLS-461:
--
I wish to modify
Download and Install is very touchy. I have mostly never been able to
get it to work when launching the plugin from eclipse, as you are
doing. It worked for me for a little while when I first started
working with Ganymede, but then stopped. I've pretty much had to give
up on developing it this
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-409:
---
Affects Version/s: 2.1.3
Fix Version/s: (was: 2.2.0)
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620631#action_12620631
]
Ashish Jain commented on GERONIMODEVTOOLS-421:
--
Other than modifying
Hi Ted,
Thanks for your reply! Yes you are correct it works fine once you have
installed it through Eclipse update manager.
Somehow it worked for Tim day before yesterday. May be he can suggest
something.
Thanks
Ashish
On Thu, Aug 7, 2008 at 7:46 PM, Ted Kirby [EMAIL PROTECTED] wrote:
Download
+1 I like it because we don't need to ask the users to install the
private repo first.
Lin
On Thu, Aug 7, 2008 at 9:13 AM, Donald Woods [EMAIL PROTECTED] wrote:
We have danced around the problem of not being able to build Samples,
Plugins or GEP from a clean m2 repo without building the
+1
Donald Woods wrote:
We have danced around the problem of not being able to build Samples,
Plugins or GEP from a clean m2 repo without building the Server's
repository subdir for long enough. I believe it is time to create the
following location in SVN -
geronimo/repo
Which would hold
Hi Ashish, it only worked for me the other day because I had first downloaded the
GEP plugin via the Update Manager. It won't work correctly if you. Your scenario
is only slightly different than the one we warned against in the following
documentation. I investigated this problem back in 2.1.0
[
https://issues.apache.org/jira/browse/GERONIMO-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun closed GERONIMO-4228.
-
install plugin from deploy tool doesn't honor load=false
[
https://issues.apache.org/jira/browse/GERONIMO-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun resolved GERONIMO-4228.
---
Resolution: Fixed
Patch committed (see subversion tab). Thanks Donald for reviewing it.
Tested
I agree in principle with creating a new location for 2.2 features to be
documented. My only concern was that we are consistent so that the
documentation will be easy for users to find and easy to integrate when
we eventually do a mass merge from 2.1 to 2.2.
So, I created a new space for
I may be misunderstanding what your proposing, Donald, but I'm not sure if
this suggestion would actually decrease the dojo footprint at all. From my
understanding, the monitoring plugin that is included in the EE servers
requires a dojox feature (charting). This would mean that the monitoring
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-421.
Resolution: Fixed
HI Ashish, actually I think that's all. It
When installing a plugin that is already existed, we still give people
confusing missingDependency message
--
Key: GERONIMO-4230
URL:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-461:
---
Assignee: Ashish Jain (was: Tim McConnell)
Thanks Ashish, I'll
Hi Rebekah,
I just posted a note about a new space that I created for the 2.2
documentation. The new space was really created just to get things
moving for 2.2. It was not a statement of what the final structure
should be ... so please feel free to continue to explore this area and
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-433:
---
Summary: GEP 2.1.2 Tasklist for Ganymede-specific problems (was:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-433:
---
Summary: Tasklist for Ganymede-specific problems (was: GEP 2.1.2
Donald Woods wrote:
We have danced around the problem of not being able to build Samples,
Plugins or GEP from a clean m2 repo without building the Server's
repository subdir for long enough. I believe it is time to create the
following location in SVN -
geronimo/repo
Which would hold our
Taskslist for Java 6 specific problems
--
Key: GERONIMODEVTOOLS-466
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-466
Project: Geronimo-Devtools
Issue Type: Task
Affects Versions: 2.1.2
Maybe I'm missing something, but aren't these artifacts already in svn
under ../repository, e.g.
http://svn.apache.org/repos/asf/geronimo/server/branches/2.1/repository/
(for the given release)? Are you proposing one main location for all
version of the artifacts for all versions of Geronimo? Will
+1 quite useful
Lin Sun wrote:
+1 I like it because we don't need to ask the users to install the
private repo first.
On Thu, Aug 7, 2008 at 9:13 AM, Donald Woods [EMAIL PROTECTED] wrote:
We have danced around the problem of not being able to build Samples,
Plugins or GEP from a clean m2 repo
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-466:
---
Summary: Tasklist for Java 6 specific problems (was: Taskslist for
Hi Ted, good ideas. Actually the GEP already has that type of warning
message.
jvmWarning={0} is currently only certified on a 1.5 JVM. Use of any other version
is not currently supported.
Also, I've opened a task-list JIRA for Java 6 specific problems as you suggest.
Could you subtasks
Great news Donald!
I guess the idea to make this new repository branch to act as a geronimo
specific maven repository that can be relied on and pointed to in
geronimo project pom:s !?!
This would (among other things) cut down the steps (and build
instructions) needed for building special
IMHO, the 2.2 space must be seeded from the 2.1 space. The question is
just when to do it. That's why I suggested creating 2.2 content under
some temporary space. Once we have the actual 2.2 space setup (from
2.1 content) then we can move these new pages into 2.2 space. It will
be a lot easier to
On Aug 7, 2008, at 9:13 AM, Donald Woods wrote:
We have danced around the problem of not being able to build
Samples, Plugins or GEP from a clean m2 repo without building the
Server's repository subdir for long enough. I believe it is time to
create the following location in SVN -
D'Oh! Thanks Tim. What does supported mean, anyway? Given that
users are hitting this problem, maybe we need to be more visible in
our warnings. Let's see where we get to with this Java 6 JIRA in the
next day or two, and adjust our documentation and possibly code
accordingly.
Thanks,
Ted
Resending somehow this never came through the first time:
Hi Rebekah,
I just posted a note about a new space that I created for the 2.2
documentation. The new space was really created just to get things
moving for 2.2. It was not a statement of what the final structure
should be ...
If our goal is to have developers create documentation for new features when
the feature is integrate, then I don't see why we shouldn't just create the
2.2 space now and seed it with 2.1 right away. If no new features are added
yet, then the old documentation applies just as much to 2.2 as it
I agree that I don't really want to see a change of structure in
documentation unless someone can give a good reason to that. I feel
I just learned on how to locate some of the good information in the
doc and I don't want to go through that learning again.
The prob of seeding 2.2 space with 2.1
On Aug 7, 2008, at 8:43 AM, Jarek Gawor wrote:
IMHO, the 2.2 space must be seeded from the 2.1 space. The question is
just when to do it. That's why I suggested creating 2.2 content under
some temporary space. Once we have the actual 2.2 space setup (from
2.1 content) then we can move these
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-439:
---
Component/s: eclipse-plugin
Affects Version/s: 2.2.0
Geronimo Revision: 683659 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080807/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080807
[INFO] BUILD
This is some great information Dave. Thanks for the details.
I experimented a little with export/restore but without much success. I
wasn't able to restore an image with an updated entities.xml (that
simply replaced the old space references with new space references).
Each time I attempted
Agree.
-Donald
Jarek Gawor wrote:
IMHO, the 2.2 space must be seeded from the 2.1 space. The question is
just when to do it. That's why I suggested creating 2.2 content under
some temporary space. Once we have the actual 2.2 space setup (from
2.1 content) then we can move these new pages
David Jencks wrote:
On Aug 7, 2008, at 8:43 AM, Jarek Gawor wrote:
IMHO, the 2.2 space must be seeded from the 2.1 space. The question is
just when to do it. That's why I suggested creating 2.2 content under
some temporary space. Once we have the actual 2.2 space setup (from
2.1 content) then
I tried building the 2.1.3-SNAPSHOT release from a clean repo earlier
today and was getting a build failure due to the following dependency in
Genesis 1.3 no longer being in the m2 snapshot repo on people.apache -
org.apache.geronimo.genesis.config:geronimo-skin:jar:1.2-SNAPSHOT
So, I
On Aug 7, 2008, at 2:29 PM, Donald Woods wrote:
I tried building the 2.1.3-SNAPSHOT release from a clean repo
earlier today and was getting a build failure due to the following
dependency in Genesis 1.3 no longer being in the m2 snapshot repo on
people.apache -
Donald Woods wrote:
I tried building the 2.1.3-SNAPSHOT release from a clean repo earlier
today and was getting a build failure due to the following dependency in
Genesis 1.3 no longer being in the m2 snapshot repo on people.apache -
In-line.
Jarek Gawor wrote:
Maybe I'm missing something, but aren't these artifacts already in svn
under ../repository, e.g.
http://svn.apache.org/repos/asf/geronimo/server/branches/2.1/repository/
(for the given release)?
True, maybe for now, pointing into tags for the required artifacts
True, but wouldn't that introduce the overhead of our release process
and voting?
Would we create a geronimo/patches subproject arranged like our specs,
where each artifact would be its own subdir and still check the patched
artifacts in for the build to use and then move them to tags after
There have recently been issues with the snapshot repository because it
was running low on space and so any snapshot older than 30 days was
deleted across the board. One reason given for the rapid growth in the
repository size was due to projects using timestamped snapshots. It was
stated
On Aug 7, 2008, at 8:26 PM, Donald Woods wrote:
True, but wouldn't that introduce the overhead of our release
process and voting?
I wouldn't call it overhead. I'd call it oversight. Our community is
releasing the patches and publishing the binaries. Server release
votes have covered
Build exception: java.net.MalformedURLException: no !/ in spec
--
Key: GERONIMO-4231
URL: https://issues.apache.org/jira/browse/GERONIMO-4231
Project: Geronimo
Issue Type: Bug
54 matches
Mail list logo
