2:53 p.m.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Minor
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or more
accurately - under certain circumstances it will stop working. E.g. I think after adding
some additional libraries to deploy to webcontent/lib. I suspect the problem is that it
gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:37 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10197:
----------------------------------------
Fix Version/s: 3.3.0.Beta1
3.3.0.M5
Priority: Critical (was: Minor)
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:37 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
Marking as critical if this is truly a regression.
Dirk, Your prose text is fun but its very hard to figure out what exactly your are doing
and where ?
Could you please attach a sample project that shows the misbehaving ?
Or at least screenshots of the deployment assembly UI before/after and with an
illustration of what output you get (i.e. use tree on command line to show output)
Thanks,
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10197:
-------------------------------------
I think after adding some additional libraries to deploy to
webcontent/lib. I suspect the problem is that it gets deleted before deploying.
I'm a little confused.. how does adding new libs to webcontent/lib end up in deleting
them before deploying? Files living inside your webcontent/lib should never be deleted by
our tools...
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
Rob - I think he means that the deployed webcontent/lib folder is empty.
Not his lib folder in his project.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:03 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen resolved JBIDE-10197.
-----------------------------------------
Resolution: Incomplete Description
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:03 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
we haven't been able to reproduce this based on the provided description.
Would love to get an example project or a better step by step description on how to
reproduce the problem.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:42 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
hmm well I'm actually having problems reproducing it with a new project. This leads me
into thinking that it might come from porting and adjusting an existing project from
eclipse 3.3 to 3.6.2 including a new jboss tools version - would that be a possible
cause?
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
if you could provide me some information on what config / properties / settings files you
could use to see what happened I'd provide them. I can easily reproduce the bug by
removing the fileset which bluntly copies ** from <projectname>/WebContent to /. As
a result not all libraries get deployed.
I cannot reproduce it with a new, simple project though (which probably solves your
worries :-) ). I would provide screenshots as well if you tell me what to screenshot.
You'll probably understand that i'll not provide our business application project
:-)
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
the .settings/ content in your project(s) would be helpful.
The one that works and the one the doesn't and we'll do a diff.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.M5, 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:32 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10197:
--------------------------------
Fix Version/s: (was: 3.3.0.M5)
This clearly has missed m5. :(
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
i'd provide the setting files but would you mind to receive them by e-mail? Since I
don't feel like uploading my project settings for everyone to see... paranoid and
stuff.
What I was able to see is that there are some entries dublicated. E.g. in the deployment
assembly view you have a list which contains, lets say libA. If you go to common.component
I can see 2 entries referring to this libA, one of which is not visible in the deployment
assembly. libA was earlier in projectA, now only exists in projectB. But... removing the
incorrect duplicate doesn't resolve the problem. The library just doesn't get
deployed.
The diff which breaks the things basically is the removal of the entry:
<dependent-module deploy-path="/"
handle="module:/org.jboss.ide.eclipse.archives.webtools.filesets.vcf.FilesetComponentResolver/path=%2FProject+A%2FWebContent&includes=**&excludes=">
<dependency-type>consumes</dependency-type>
</dependent-module>
Tell me whom I should mail the settings
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
so where are we standing now? I guess in the Christmas preparations ;-)
would be a different way to work around the probably caused unclean configuration problem
by deleting all the settings files to reset them? e.g. just overwrite them with newly
generated config files and start from scratch?
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:05 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
that should fix it yes if things work yes - for looking at it in details it will have to
wait after the xmas break ;(
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:07 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
how to correctly clean things? I tried deleting and/or removing everything inside
org.eclipse.wst.common.component but it had some side effects which I didn't realize
in the first place and cost me some time. I'll look into it again when I have some
time since a couple files won't get hot deployed on change.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:44 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
is it everything in the org.eclipse.wst.* files of eclipse? or only the
org.eclipse.wst.common.components file? since I basically have to test all dependencies of
the application after that change again, i'd be jumping and laughing if someone can
give me this information
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10197:
-------------------------------------
The only real one we care about is org.eclipse.wst.common.components
We would want to see that file and anything inside it. You can add a comment before and
after the line whose removal breaks the deployment.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Critical
Labels: jboss
Fix For: 3.3.0.Beta1
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10197:
--------------------------------
Fix Version/s: 3.3.x
(was: 3.3.0.Beta1)
Priority: Major (was: Critical)
Component/s: UpStream
This is not something we have the time to investigate at this time. The fix would be
upstream anyway, and would have to wait for the next major release.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:25 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar updated JBIDE-10197:
--------------------------------
Attachment: org.eclipse.wst.common.components
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
Attachments: org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar updated JBIDE-10197:
--------------------------------
Attachment: org.eclipse.wst.common.components
same as before but this time with a comment to show which removal of entry will break the
deployment
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:34 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar commented on JBIDE-10197:
-------------------------------------
I uploaded the file, the second one has a comment to show which entry removal leads to the
problem. Basically, it is the first occurrence of <dependent-module
deploy-path="/" ... if you remove it, it won't deploy correctly - e.g. 95%
of the libraries are missing.
btw: my team and I have generally problems now with the deployment, sometimes it
won't update changed websites and a full republish is required or restart of web
application. Things were just running ways better with the old (3.3) version of eclipse.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:34 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Dirk Dollar edited comment on JBIDE-10197 at 3/19/12 8:33 AM:
--------------------------------------------------------------
I uploaded the file, the second one has a comment to show which entry removal leads to the
problem. Basically, it is the first occurrence of <dependent-module
deploy-path="/" ... if you remove it, it won't deploy correctly - e.g. 95%
of the libraries are missing. You can delete the first file I uploaded, I don't know
how to do it myself
btw: my team and I have generally problems now with the deployment, sometimes it
won't update changed websites and a full republish is required or restart of web
application. Things were just running ways better with the old (3.3) version of eclipse.
was (Author: Toskan):
I uploaded the file, the second one has a comment to show which entry removal leads to
the problem. Basically, it is the first occurrence of <dependent-module
deploy-path="/" ... if you remove it, it won't deploy correctly - e.g. 95%
of the libraries are missing.
btw: my team and I have generally problems now with the deployment, sometimes it
won't update changed websites and a full republish is required or restart of web
application. Things were just running ways better with the old (3.3) version of eclipse.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10197:
---------------------------------------------
any reason why you have a mix of getting things from the classpath and getting things from
external resources ?
This should of course work but just wondering why you don't get it all from your
classpath ?
btw. we cannot reproduce this at the moment so we are kinda shooting in the dark here -
you are saying you have other issues, please
report them separately with as much details as you can provide on it.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: 3.3.x
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 p.m.
[
https://issues.jboss.org/browse/JBIDE-10197?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10197:
--------------------------------
Fix Version/s: LATER
(was: 3.3.x)
The only thing I can think of after plenty of time testing is that this is related to
JBIDE-7472, which is a much earlier bug that's been around for a long long time,
upstream in WTP. It seems their classpath container actually scans the contents of
webinf/lib, and adding or removing files to it has always been... ... ... dangerous.
Putting files directly in the folder has never worked as we wanted it to, from the
beginning.
Most of the biggest bugs were cleared out, but there were always ones like this left,
which were difficult and inconsistant to replicate. JBIDE-7472 relates to removal of files
from web-inf/lib, and this one seems to relate to adding files there directly.
I wish there was more that could be done, but at this point, I'm stumped.
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Labels: jboss
Fix For: LATER
Attachments: org.eclipse.wst.common.components,
org.eclipse.wst.common.components
This is my first bugreport... if I'm doing something wrong or chose the wrong
component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving
similarly (but differnt) to older versions when it was used under a different name (J2EE
module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or
more accurately - under certain circumstances it will stop working. E.g. I think after
adding some additional libraries to deploy to webcontent/lib. I suspect the problem is
that it gets deleted before deploying. The workaround for me was to use a fileset of the
<projectname>/WebContent folder and to point it to an empty deploy path - and to
scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4364
days inactive
4684
days old
jbosstools-issues@lists.jboss.org
23 comments
10 participants
participants (10)
-
Dirk Dollar (Commented) (JIRA) -
Dirk Dollar (Created) (JIRA)
-
Dirk Dollar (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Max Rydahl Andersen (Resolved) (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Rob Stryker (Commented) (JIRA)
-
Rob Stryker (JIRA)
-
Rob Stryker (Updated) (JIRA)