Code assist will be really helpful as the documentation is not that good.
-
Key: MNGECLIPSE-167
URL: http://jira.codehaus.org/browse/MNGECLIPSE-167
Project: Maven 2.x Extension fo
Changelog produces empty output.
Key: MCHANGELOG-42
URL: http://jira.codehaus.org/browse/MCHANGELOG-42
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-1
Environment
Changelog not getting created properly.
---
Key: MCHANGELOG-43
URL: http://jira.codehaus.org/browse/MCHANGELOG-43
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-1
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_71976
]
Abhijit Diwan commented on MCHANGELOG-43:
-
When I ran
p4 filelog -tl //EJB/ejb-dev/MavenCodeline/AeConnector
I get the same error what
[ http://jira.codehaus.org/browse/MCHANGELOG-42?page=comments#action_71985
]
Abhijit Diwan commented on MCHANGELOG-42:
-
It worked thank you very much for help but I feel we should have update about
the repositories to point to. Now my pl
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_72100
]
Abhijit Diwan commented on MCHANGELOG-43:
-
In order to find the changelog it needs to log in to perforce right. What is
point in giving the local path of perfor
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_72284
]
Abhijit Diwan commented on MCHANGELOG-43:
-
It is like any other SCM where you check-out and have working copy of the
project locally on your development machine
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_72439
]
Abhijit Diwan commented on MCHANGELOG-43:
-
No actually I had problem where the configuration is not able to log to
perforce. If you define $P4PORT then you do n
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_72527
]
Abhijit Diwan commented on MCHANGELOG-43:
-
Yes I thought initially it was bug with the plug-in that is why I reported it.
You can close the jira if this is no l