[
http://jira.jboss.com/jira/browse/JBIDE-2211?page=comments#action_12413918 ]
Rob Stryker commented on JBIDE-2211:
------------------------------------
I just want to comment and say I'm not sure if GA will please reporter on this issue.
Basically, it could still say 0 files changed if no resources have changed in teh
WORKSPACE. It will be listing specifically how many WORKSPACE resources have changed,
which will have NO bearing on whether or not a jar is coppied or not.
Remember, any FULL publish will republish everything. A new jar will be created and
published. So if you re-publish twice, full, the event log on the second publish event
will still say no resources have changed... but a new output jar *is* created and *is*
published to the server.
Effectively, I've standardized on listing resource change counts and have changed the
text slightly to reflect that. But it is still possible submitter will still see 0
resources changed, and yet a new jar is created.
Event log "Publishing... " message can sometimes be
misleading
--------------------------------------------------------------
Key: JBIDE-2211
URL:
http://jira.jboss.com/jira/browse/JBIDE-2211
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.1.0.CR1
Reporter: Galder Zamarreno
Assigned To: Rob Stryker
Fix For: 2.1.0.GA
> If the archive had actually changed and the publish has really occurred,
> > you get:
> >
> > -> Publishing [1 modules, 0 files changed]
> > -> [Full, Changed] .jar
> >
> > I have to extend the event to actually realise that the jar changed was
> > actually published, even thought the title of the even still says "0
> > files changed".
That sounds like a bug - please put in jira.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira